On 25-01-13 17:35, Derek Atkins wrote:
Just for the record, the things left to do are:

1) get gitolite to push to github -- this will require a github reset
2) convert www to use git and get gitolite to signal an update instead
    of svn
3) send emails from gitolite instead of svn

I think we're mostly ready for point 1. I have just successfully concluded some extra tests in the gnucash-docs repo.

What I did was I set up a committers repo based on gitolite instead of github and pushed some changes trough via svn dcommit. This added commits in both github (via svn->git@John's->github) and gitolit (via svn->g...@code.gnucash.org).

After a git update in both repos, I compared the commits and they were identical. Except for the hash refs of course due to modified history.

The only thing left to do before the reset is to inform other people that may have cloned the repos about it.

Following John's suggestion that means:
- contacting the few people that have forked on github (is there a way to notify them from within github ?)
- a news message on the main website
- replicate the news message on facebook/google+/linkedin

I'm not sure if we have to inform in advance, or only together with the reset. Most people won't be able to update until after the reset anyway, but on the other hand it's probably more polite to share information in advance. That would give anyone with a good reason to postpone the reset some time to react.

What do you think ?

Geert
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Reply via email to