Andrew Dunstan wrote: > >Yes, I had thought about that --- I put something about migrating to 7.3 > >on a web page and put the URL in the release notes, and the URL kept > >becoming invalid as they changed web configurations. I am afraid we > >have to keep this in CVS so we don't lose it over time. > > > >It could be huge. Current release notes for 7.4 is around 500 lines. I > >think I could do this in another 500 lines. > > > > This is starting to sound awfully like a conventional bug tracking > system but without the support infrastructure. Why not go the whole > distance? Then your release notes could give the numbers and headings of > bugs fixed (including features added) and those who want more details > could look at the bug reports. The process could be a whole lot less > painful than it appears to be right now, I suspect.
Bug tracking systems have the same limitation as incremental release notes --- youi have to do a lot of piecemeal work to get complete output at the end, rather than doing it more efficiently in one batch. Most people working on PostgreSQL are volunteers, and one of my primary jobs is to make it easy for them --- if it takes me a week to get the release notes together --- so be it --- I am making it easier for others. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
