On 03 Mar 2003 10:32:36 +0100, Dominik Vogt wrote: > > On Mon, Mar 03, 2003 at 02:07:10AM +0000, Mikhael Goikhman wrote: > > > > On Fri, Feb 28, 2003 at 11:08:58AM +0100, Dominik Vogt wrote: > > > > > I think we have too many messages in the NEWS for the unstable > > > > > branch right now. In the past, I made entries for > > > > > > > > > > * New features and other important user visible changes > > > > > > > > > > but not for > > > > > > > > > > * Bug fixes > > > > > * Minor user visible changes > > > > > * Changes in the documentation > > > > > > > > > > Especially, when a feature was introduced in the unstable branch > > > > > and removed before the stable release, I remove any hints of that > > > > > feature from the NEWS. If it is renamed before a stable release, > > > > > I replace its former name in the NEWS with the new name and do not > > > > > add a "renamed foo to bar" message in the NEWS. > > [snip] > > > But I would not add anything above these 3 types. If there is a question > > whether a change is minor or not, it is not minor, say, changes in spaces > > or quotes may be considered minor, but not a name change. > > > I *definitely* > > want to see all user syntax changes in 2.5.x, 2.5.x+1, 2.5.x+2 sections. > > Users use different versions, probably all of these, you can't provide a > > support without pointing to versions when syntax was changed. For example, > > I wanted to know when Style Border was renamed to Borders and I needed to > > grep ChangeLog for this, because from just looking at NEWS it may seem > > that there was never be "Border". Not very good for me. > > My approach is simple. In the stable branch: > > - All code changes are mentioned. > - The NEWS for the beginning of a stable branch contains a > summary of all user visible changes. > > And in the unstable branch: > > - Bug fixes are usually not in the NEWS. > - All new features that appear in the unstable branch may be > changed, renamed or removed without notice.
Agree for the pre-alpha versions. But when 50% or more of the messages on fvwm@fvwm.org speak about 2.5.x I would prefer to start to have NEWS that looks somewhat between these two opposite approaches. Regards, Mikhael. -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
