Re: Separate release notes for each release?
[EMAIL PROTECTED] writes: > > Yes, but it also takes me extra time. (I'm a lazy bum). You can > > subscribe to [EMAIL PROTECTED] to get the latest scoops. > > Thanks for the tip. You should mention this list on > > http://lilypond.org/web/documentation.html > > where you should also change "Bugreports" to "Bug reports". done. > > -- > http://www.mupsych.org/~rrt/ > Astrophysics: it's not exactly rocket science -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: Separate release notes for each release?
> Yes, but it also takes me extra time. (I'm a lazy bum). You can > subscribe to [EMAIL PROTECTED] to get the latest scoops. Thanks for the tip. You should mention this list on http://lilypond.org/web/documentation.html where you should also change "Bugreports" to "Bug reports". -- http://www.mupsych.org/~rrt/ Astrophysics: it's not exactly rocket science ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: Separate release notes for each release?
On Wed, 25 Feb 2004, Han-Wen Nienhuys wrote: > [EMAIL PROTECTED] writes: > > As well as the cumulative 2.0->2.1 release notes, it would be very helpful > > to have per-release release notes, so one can see what has changed between > > individual releases. > > Yes, but it also takes me extra time. (I'm a lazy bum). You can > subscribe to [EMAIL PROTECTED] to get the latest scoops. > Or, for detailed information, look into ChangeLog in the top directory, search for "VERSION" (which usually appears whenever a new version is released), and look at the entries inbetween. Note however, that due to frequent code redesign this detailed source of information may often contain inconsistencies (such as in the case of LyricVoice). Greetings, Juergen ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Separate release notes for each release?
[EMAIL PROTECTED] writes: > As well as the cumulative 2.0->2.1 release notes, it would be very helpful > to have per-release release notes, so one can see what has changed between > individual releases. Yes, but it also takes me extra time. (I'm a lazy bum). You can subscribe to [EMAIL PROTECTED] to get the latest scoops. > > Also, it seems the 2.0->2.1 release notes is getting a bit inconsistent: > for example, in one place it says LyricVoice no longer exists, while lower > down it talks about a change to LyricVoice. fixed. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: Separate release notes for each release?
[EMAIL PROTECTED] writes: >[the NEWS file] > Are new changes always added to the top? Yes. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: Separate release notes for each release?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday February 24 2004 19:05, Reuben Thomas wrote: > As well as the cumulative 2.0->2.1 release notes, it would be very helpful > to have per-release release notes, so one can see what has changed between > individual releases. Dates attached to the changes, or what version they were changed for would be two useful ways to doc that. Are new changes always added to the top? -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAPC4i+mws0jizTrwRAnSnAKDV3nfGlui5dJOPNsJtNIC+v1D90gCg5Eqq QK5BtHT+CdDhyPcjxkeD2Ig= =BMAW -END PGP SIGNATURE- ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Separate release notes for each release?
As well as the cumulative 2.0->2.1 release notes, it would be very helpful to have per-release release notes, so one can see what has changed between individual releases. Also, it seems the 2.0->2.1 release notes is getting a bit inconsistent: for example, in one place it says LyricVoice no longer exists, while lower down it talks about a change to LyricVoice. -- http://www.mupsych.org/~rrt/ The yak is slow but the earth is patient (LucasArts) ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
