On Mon, Aug 27, 2012 at 1:55 PM, Johan Tibell <span dir="ltr">&lt;<a href="mailto:johan.tibell@gmail.com" target="_blank">johan.tibell@gmail.com</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div id=":1ok">Development takes place on the master branch which is, some time<br>
before the release, forked into a cabal-x.y branch. The cabal-x.y<br>
branch will only receive bug fixes up til the release. General<br>
development (i.e. new features) continue going in to the master branch<br>
at all times. We need to merge bug fixes from the cabal-x.y branch<br>
back into master, at a minimum after the release of that branch.<br></div></blockquote></div><br><div>That sounds fine to me.</div><div><br></div><div>Other small details:</div><div><ul><li>We should bump the cabal-install package version to be the same as the Cabal package version, and increment both at the same time. It&#39;s deeply confusing to have the two out of sync.</li>
<li>I&#39;d like to get rid of some old named branches that no longer have any value, e.g. cabal-1.2. Keeping tags around for a long time makes sense, branches do not.</li></ul></div>