Trevor, On 30/08/15 16:57, Trevor Daniels wrote: > > James wrote Sunday, August 30, 2015 4:22 PM > >> I've 'synced' my list of Patches I've been keeping track of >> manually with the issues list now. >> >> Is this set of issues going to be the one we migrate to the 'new' >> non-SF system? >> >> I.e. do we now treat this as a live system? > > Yes. When we migrate to Allura at Savannah I will export from this > SF system and import to the Savannah system. I shall not be > returning to GoogleCode (unless some disaster befalls). > > Now you've completed your work I'll invite the Bug Squad to join up > so they can continue their work in catching new issues. > > I've not heard anything from Federico or Josiah for over a week, so > I've no idea what state Allura at Savannah is in. I suggest we > wait a few days for news before inviting devs to join at SF, in > case the Savannah system comes on line soon. Are you willing to > update the DB with pushes when they occur for a few days? >
Not a problem - how I 'display' those in the PATCHES email is something I need to work on, as the make-countdown-announcement.sh no longer works. @everyone: So from now on (unless anyone thinks I shouldn't), I won't be updating Rietvelds with PATCH statuses anymore, but using SF instead. If I find anything in my current list that doesn't have an issue in SF (for whatever reason, I will add it and will 'own' that - each issue has to have an email of the owner - and ask that dev to register so they can take the issue themselves. @Trevor Assuming that you eventually start the migration, I assume you'll tell the group and we'd best hold off updating SF until it is completed (so that we don't interfere with the migration)? James _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
