On Friday 08 February 2008, Juha Heinanen wrote: > > Maybe a new list (like "[EMAIL PROTECTED]") where a developer, > > after making the fix, can issue (if considered important) an update > > alert for the interested people : > > Severity: > > Affected services/modules: > > Description: > > Rev number where the fix is available: > > How to update: ? > > good idea, but perhaps Severity and How to update can omitted, since all > messages ending to this list should fix a severe problem and update > instructions can be found elsewhere.
I think most people have aggreed that this "announce" list would be a good idea. If we can restrict this to short messages and only for severe problems, then i would support this too. What i don't want (as expressed in my previous mails) is to promote the stable branch as a replacement for minor releases, and subsequently neglect them in the long run. If somebody choose to run from the stable branch, then he must also invest some time to follow the changes that are done "his" branch. I don't want to increase the workload for bugfixes in the stable branch for the developers, as this is already a boring and unpopular work. If one must write a lengthy announcements for every backport, then i worry that fewer people care about this branches and the backport of their fixes. Henning _______________________________________________ Devel mailing list [email protected] http://lists.openser.org/cgi-bin/mailman/listinfo/devel
