On Tuesday 31 March 2009 20:19:08 Matthew Toseland wrote: > Which DSCM should we switch to? Last time we discussed this, we decided on > mercurial (hg). We need a decision in the near future - it has dragged out > for 6 months due to technical and communication problems, but nextgens is > able and willing to implement a change in the near future. Ian has suggested > that we need to re-evaluate the decision. So, we will take a vote of > developers active in the last 6 months - and if nobody votes, I'll choose. > > The reasons we chose hg previously: > - It has a better HTTP transport. > - It has better Java support : in particular, netbeans has integrated and well > supported hg support. > - It has better Windows support : mainstream hg runs on Windows, while there > are Windows Git clients. > > Both hg and git have been demonstrated to work over Freenet. Git seems to need > a bit more help than hg does. > > At least four developers and at least one third party have been maintaining > their own svn-to-git repositories based on remotely importing the official > tree, this is one of many reasons to use a DSCM: > - Better offline commit support. > - Better redundancy and security in general. > - Better integration with anonymous development (subject to the caveat that we > must be sure something is the contributor's own work). > > In order to get a clear-cut decision, I have set an arbitrary deadline of the > end of Tuesday the 7th of April. This will only be extended in *exceptional* > circumstances. > > So if you have an opinion, please reply to this thread. If you qualify as a > developer active in the last 6 months, then please indicate your vote - you > can change it right up to the deadline. > Okay, the deadline has passed. Votes:
In favour of git: sanity (has committed recently, if not code!) bombe robert tommy[d] In favour of hg: saces nextgens Abstaining: sdiz Anyone I've missed? Assuming I haven't missed anyone and there are no disputes, clearly git has it. The decision will be implemented soon, using github, and not keeping history. SVN will be made to be read-only and the archive will be published and new git repositories will be created on github. Stable builds will be tagged and signed and built by me, and we will need to create a similar arrangement for plugins. I will announce when this is going ahead, it won't be immediately. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 835 bytes Desc: This is a digitally signed message part. URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20090408/caea977e/attachment.pgp>
