[tahoe-dev] David-Sarah will be Release Manager for the next release.
zooko at zooko.com
Thu Mar 29 22:18:03 UTC 2012
Another major issue that David-Sarah and the rest of us have to decide
is whether to do the next release with both git and darcs in play or
cut over entirely to git (#1644).
I drew attention to this situation by forgetting that we were supposed
to push changes into trunk solely through darcs, and I committed some
patches to fix #1692 to my personal tahoe-lafs git repo on github:
David-Sarah naturally didn't see this, so they went ahead and fixed
the same issue slightly differently:
So this was duplicated effort, and it also means someone (me) has to
manually merge tahoe-lafs trunk with my tahoe-lafs repo if they (I)
don't want to throw away my changes.
I note that the "how_to_make_a_tahoe-lafs_release.org" file, which was
last touched by Brian while he was Release Manager for 1.9.0 and
1.9.1, now specifies to get all of the source code exclusively from
git and not use darcs:
(That doesn't mean that we have to stop using darcs to *commit* patches.)
tickets mentioned in this letter:
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1644# move to git
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1692# FTP frontend
should not be more prominent than SFTP in any of the documentation
More information about the tahoe-dev