Nils Kneuper <[email protected]>: > I just wanted to ask what the current progress in regards to the move to git > is. The last thing I know is that I gave esr some extended access to our > project at sf.net so that he can do some further testing.
Ah, I didn't know that had been done. I see I now have admin permissions.
That is good; I think it's all I'll need to set up a git repo there.
> * Mapping of gna/gnu accounts to names and email addresses: completed?
Essentially completed. We have a couple I've been unable to identify:
"zas" and "uso". Also a bunch of obviously mechanically generated names
of the form uid[0-9]+ that seem to have been related to patches forwarded
from the forums. But we have good mappings for all active devs and almost
all historical ones.
> * Problematic branches in our svn history: everything solved and done?
Not quite. Most are solved, but the following branches do not have a
known disposition yet:
# 1_2:
# editor:
# fendrin_gui_stuff:
# fendrin_pathfind_and_editor:
# mp_registration: Might have been merged at r28628, investigate.
# umcmg:
I don't know who owns mp_registration. I think I can settle all but that given
a bit of conversation with fendrin and Shadowmaster.
> * Decision about our new host: Last I know is that we basically came down to
> either going sf.net or something "selfhosted". Any news / changes here?
I think what we need is for our release manager (you!) to make a firm
decision about where he will make releases from. I favor moving to sf.net;
I don't think we need the complication of self-hosting.
> * Bugtracker: Was anything said/decided about how to progress with the bugs
> database?
Yes, we have a volunteer (Crab) to migrate it, but that probably won't be done
until after the repo move.
> It would be good to have one mail summarizing all the relevant points (what
> was done and what is left to do) of the migration so that we can finally get
> done with it.
I want to get this done, too. It has become something of a time sink for me.
The good news is that I have a working lift script that repeatably
produces a clean git repo in about half an hour of processing. (I
actually had to upgrade my desktop, installing more memory and a new
drive, because the repo is so freaking huge.)
Only very minor modifications of the lift will be required to do a
final conversion. The hard and time-consuming part is done.
> 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
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.
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.
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.
6. (unassigned) The move will probably require minor build-system changes.
Someone (again, not me) needs to be paying attention to that.
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,
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.
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
signature.asc
Description: Digital signature
_______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
