-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 20.03.2013 15:43, schrieb Eric S. Raymond: > Most of the old branches now either have merge points to trunk or have been > identified as failed experiments and deleted. The author map is as > complete as it is likely to get (we still have not identified 'zas' and > 'uso'). SourceForge has been chosen. The build systems have been updated > to be git-aware. We have just shipped a release. > > I have verified that a normal scons build is possible from the git repo. > > We are as prepared for migration as possible. Ivanovic, you should choose > Blue Day (when the git repo goes live) and Red Day (when we consider the > Subversion repo dead and stop copying new revisions from it to the new > repo).
Okay, now that 1.11.2 is done, the dates are set: 1) Blue day: right now! 2) Red day: Easter Sunday, 19:00 GMT+1 (local time in Germany) > The new repo, after aggressive garbage collection, is 2.57GB. > > Unfinished tasks: > > 1. Bugtracker migration > > 2. Wesnoth wiki updates > > I have run into an odd technical problem with the latter. I renamed > WesnothSVN to WesnothRepository, preparatory to changing that page to > describe basic repository operations using git. The WesnothRepository page > definitely exists, with WesnothSVN now a redirect to it. > > But when I try to replace links to WesnothSVN with links to > WesnothRepository, the wiki insists the latter page does not exist. Any > assistance from people more familiar with the wiki's quirks would be > appreciated. Okay, the problem with the wiki page was solved. "We" now just have to make sure that we have some easy migration guidelines for those not too used to git (like e.g. me). Things the guideline should cover: 1) initial checkout of "what once was trunk" 2) building from the checkout 3) committing to branches (e.g. to the stable 1.10 branch for i18n updates) 4) creating and working with own branches What we have decided on is to be using sourceforge as git host. I don't know what "the admin team" needs to do to add accounts with commit access there. Maybe esr can clear this up. Other things to do now: 1) Please be patient and do try to not commit anything into svn at gna.org since esr is right now working on the migration. 2) Wait for the announcement by esr with the url to the git repo. 3) Get yourself a git checkout. 4) Starting easter Sunday (unless something drastic happens) the old svn repo will be "soft closed" meaning you could still commit things there, they will just not be used in releases or anything... Cheers, Nils Kneuper aka Ivanovic -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlFPDHAACgkQfFda9thizwUEIwCeLYvn5ggDwHKrZYb5pcZLEoJc 9WAAn1onNwFnTo7IOMGpu5zAEizTaOr+ =KUEj -----END PGP SIGNATURE----- _______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
