easiest way to help releases: adopt patchy
Patchy has helped us avoid breaking git master a few times recently, but each time involves a certain amount of my time and energy. I need to check the logs to see if it was just an accident, look through the git history to see if there's any particularly suspicious commits that may have caused it, try again without those commits, repeat, and then finally branch the entire staging and start over from scratch. This eats up time that I could otherwise spend on releases or organizing stuff. Nothing in Patchy requires my unique skills. There's a few more things that could be done to improve things, but those can pretty much just follow the existing pattern. If somebody else could take over Patchy -- even if only the staging stuff, not the new patches -- that would free up time I could spend solving release-critical bugs. If somebody could handle the new patches as well, that would be even better. We could easily have two separate people doing staging and new patches. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: easiest way to help releases: adopt patchy
Graham, On 8 January 2012 13:39, Graham Percival gra...@percival-music.ca wrote: Patchy has helped us avoid breaking git master a few times recently, but each time involves a certain amount of my time and energy. I need to check the logs to see if it was just an accident, look through the git history to see if there's any particularly suspicious commits that may have caused it, try again without those commits, repeat, and then finally branch the entire staging and start over from scratch. This eats up time that I could otherwise spend on releases or organizing stuff. Nothing in Patchy requires my unique skills. There's a few more things that could be done to improve things, but those can pretty much just follow the existing pattern. If somebody else could take over Patchy -- even if only the staging stuff, not the new patches -- that would free up time I could spend solving release-critical bugs. If somebody could handle the new patches as well, that would be even better. We could easily have two separate people doing staging and new patches. I can do that, I assume it was pretty much what I was doing with the early itteration of whatever script was on your https://github.com/gperciva/lilypond-extra site. I'm not able to do any python tweaking but I can run stuff and check things like I used to do. Let me know and if there are any specific instructions I need to set up. -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: easiest way to help releases: adopt patchy
On Sun, Jan 08, 2012 at 01:46:44PM +, James wrote: If somebody else could take over Patchy -- even if only the staging stuff, not the new patches -- that would free up time I could spend solving release-critical bugs. If somebody could handle the new patches as well, that would be even better. I can do that, I assume it was pretty much what I was doing with the early itteration of whatever script was on your https://github.com/gperciva/lilypond-extra site. I'm not able to do any python tweaking but I can run stuff and check things like I used to do. Let me know and if there are any specific instructions I need to set up. Start by running lilypond-patchy-staging.py. You'll need to tweak the config file so it emails you instead of me. Once you've run it a few times manually and had it work, stick it in a cronjob. Whenever it breaks, find out why, deal with the commits, etc. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: easiest way to help releases: adopt patchy
James, 2012/1/8 James pkx1...@gmail.com: Graham, On 8 January 2012 13:39, Graham Percival gra...@percival-music.ca wrote: If somebody else could take over Patchy -- even if only the staging stuff, not the new patches -- that would free up time I could spend solving release-critical bugs. If somebody could handle the new patches as well, that would be even better. We could easily have two separate people doing staging and new patches. I can do that, I assume it was pretty much what I was doing with the early itteration of whatever script was on your https://github.com/gperciva/lilypond-extra site. feel free to mail me whenever you need any help. I actually like playing with git from time to time. cheers, Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: easiest way to help releases: adopt patchy
Graham, On 8 January 2012 13:55, Graham Percival gra...@percival-music.ca wrote: On Sun, Jan 08, 2012 at 01:46:44PM +, James wrote: If somebody else could take over Patchy -- even if only the staging stuff, not the new patches -- that would free up time I could spend solving release-critical bugs. If somebody could handle the new patches as well, that would be even better. I can do that, I assume it was pretty much what I was doing with the early itteration of whatever script was on your https://github.com/gperciva/lilypond-extra site. I'm not able to do any python tweaking but I can run stuff and check things like I used to do. Let me know and if there are any specific instructions I need to set up. Start by running lilypond-patchy-staging.py. You'll need to tweak the config file so it emails you instead of me. Once you've run it a few times manually and had it work, stick it in a cronjob. Whenever it breaks, find out why, deal with the commits, etc. OK no problem. I'll not get to this proper until this evening and then only to give it a once over - I'm sure it will be as before - but I'll aim to start using it 'in anger' by tomorrow evening if that's ok? regards -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
