<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 16 Jul 2013, at 15:32, Andy Buckley wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Anyway, the general point is that we should review changes to the API<br>carefully rather than just dropping them in -- we have a lot of users<br>now, so should avoid flip-flopping the interface design in-between every<br>release. And I also need to learn a bit more about how best to work with<br>feature development branches in hg/git!</span></blockquote></div><br><div>Absolutely - I had not intended the tagging additions to the API to end up in the main trunk just yet. What threw me was I thought the tagging feature was safely encapsulated in its own branch (as was the gzip stuff), when in fact the tagging stuff was in a clone of the main default branch, so when it got pushed it went on the main default. Having a clear statement on when to use clones and when to use branches (and why!) would be pretty useful to me. </div><div><br></div><div>In fact, if we want to freeze development for 2.0.0 then would it make sense if there was a 2.0.0 release candidate branch (probably from Frank's previous commit?), which would allow general development to continue on the trunk, rather than having a panoply of different development clones/branches for each new feature?</div><div><br></div><div>cheers,</div><div><br></div><div>James</div><div><br></div></body></html>