-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 10.03.2013 13:00, schrieb Eric S. Raymond: >> In the wiki I found [1] but I am not sure if this is kept up to date >> and/or if some things are missing there. > > Here is my list of things to be done: > > 1. (you) Decide our hosting target
With the given options: sf.net > 2. (me) Resolve the status of those branches - either by adding proper > merge points to trunk, deleting them, or documenting that they are unmerged > but retained for historical reasons > > 3. (you) Set two transition dates, Blue Day and Red Day. They should > probably be no more than a week apart. I want to have a release of trunk and stable out before we move over, just to be on the safe side. If everything goes well this might be next weekend (Sunday) as earliest possible date. > 4. (me) On Blue Day, I will create and make available the git repo at our > new host. Devs *should* migrate to committing there at that point. Meaning that the general procedure for the move would be: 1) announce we will move at "date" 2) ask all devs to not commit anything for some hours, better one day 3) get the new repo to run 4) ask the devs to switch over and no longer commit to gna.org 5) make sure all documentation is updated to point to the new source repo 6) after "some days" somehow make sure that anything committed to gna anyway is ported over, then "close" our svn at gna.org (no idea how to do so) > 5. (unassigned) Between Blue Day and Red Day the new repo will be > considered in beta. Someone (not me) needs to step up to update the wiki. Update the wiki *where*? Having some kind of list regarding what needs updating would be helpful. Do you think anybody has such a list or can easily generate it? > 6. (unassigned) The move will probably require minor build-system changes. > Someone (again, not me) needs to be paying attention to that. As far as I am aware what needs to be changed is "just" the version number assignment for the titlescreen. Loonycyborg (scons) and Mordante (cmake) are probably the best bet for adjusting those to handle this addition of the version number differently. > 7. (you) On Red Day, providing there have been no show-stoppers, announce > tht the git repo is out of beta, you will be cutting releases from it, and > the SVN repo is decomissioned. Add a final commit explaining this and > pointing to the new location, Easy enough to do. > 8. (Crab) Bugtracker state migration. > >> PS: Has someone already prepared some "using git instead of svn and how >> to migrate" documentation? > > Not that I know of. Okay, I think we need the documentation in place before we can actually get the "real" move down and done. Meaning we can prepare everything before, but only conduct the move once we have things documented so that anybody can use the stuff easily. Cheers, Nils Kneuper aka Ivanovic -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlE8i1EACgkQfFda9thizwWh0gCfdZ2949l+dGbWjU+NY6oS21KA SUAAoJR9Hcfl5rea7NSecsb5QTtZ9ugw =AitV -----END PGP SIGNATURE----- _______________________________________________ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev
