[dev] automatic release notes (was: [dev] REMINDER: use specification templates for specifications)

2007-11-14 Thread Frank Schönheit - Sun Microsystems Germany
Hi Bernd, Looking into the allfeatures mailing list (did I already say kudos to you for working around collab.net's bug, so this list now works, again?), of the last 10 feature mails, 8 contained a specification link, where 5 referred to older-and-extended specs (including the broken one). Means

Re: [dev] automatic release notes

2007-11-12 Thread Cor Nouws
Frank Schönheit - Sun Microsystems Germany wrote (11-11-2007 22:14) While we are at it ... Somebody should look at those notes *before* they're published. It's nice to have automatisms, but as with other automatisms, there's a need for manual post-work. In this case, IMO it's a strong need. In

Re: [dev] automatic release notes

2007-11-12 Thread Frank Schönheit - Sun Microsystems Germa ny
Hi Cor. Could this meet 'your' needs, Frank http://wiki.services.openoffice.org/wiki/New_Features_2.3#Full_list Ah, that's cool! Who is in charge of this page? Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems

Re: [dev] automatic release notes

2007-11-12 Thread Cor Nouws
Hi Frank, Frank Schönheit - Sun Microsystems Germany wrote (12-11-2007 11:32) Could this meet 'your' needs, Frank http://wiki.services.openoffice.org/wiki/New_Features_2.3#Full_list Ah, that's cool! Who is in charge of this page? The volunteer :-) Inspired by the good work done by Sophie in

[dev] automatic release notes (was: [dev] REMINDER: use specification templates for specifications)

2007-11-11 Thread Frank Schönheit - Sun Microsystems Germa ny
Note that everywhere where there is a feature-info: in the Spec. abstract column of the Release Notes the process used a dirty fallback Why is that fallback dirty? I don't think that everything mentioned in the release notes needs a full blown specification. Seconded. /me too The dirty