2011/9/11 Graham Percival <gra...@percival-music.ca>: > Does anybody here feel like organizing tasks? We have a lot of > "delayed maintenance" stuff that is going to come back and bite us > in an unpleasant manner. > > 3) a full regression test examination: it's been about 5 years > since anybody actually looked at all the regtests. (we've been > doing comparisons, but not looking at all 1000+ regtests) > Phil wrote a very nice web app that makes it easy to do this -- it > randomly gives you regtests, you give feedback, it makes reports, > etc... but that was back in January or February, and it went > nowhere because nobody wanted to organize getting volunteers to go > through them. > > What a shame! This web app would be perfect for a "10 minutes a > day coffee break" thing; we could easily have a dozen casual > volunteers verify the entire regtests in a month or two. (with > each regtest being examined by at least 3 people!) > > > 4) documenting every regtest. IIRC the last time we (tried to) > make sure that all features in the regtests were in the main > documentation was back in the 2.11 days. Again, the bulk of this > work is simply recruiting and organizing volunteers; we don't need > one person to volunteer to examine all 1008 regtests. > > Once that job is done, it will be very easy to keep the > documentation up-to-date; we just run something like > git diff -u -r release/2.14.0-1 -r release/2.15.11-1 \ > input/regression/ > > to find out what new/changed features needs updating. But that > only works if we have a stable base to work from...
I might be willing to do this (since there are no other volunteers). Can i see this web app? > 1) Neil has volunteered to handle LSR -> 2.14. Great! > > 2) James has offered to reclassify issues. Great! Is there anything that should be done with regard to these two or do you post them as examples only? cheers, Janek _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel