Right now, I'm using the Maven changelog as a cut-and-paste guide to the release notes. I think the change plugin could be a replacement for this, especially if we start release more than one product, each of which could have their own change file. (struts-core, struts-opt-taglibs, struts-opt-el, struts-opt-apps, and so forth.)
I do agree that that we need to summarize the changelog to turn data into information, and the changes plugin might be a help with that. Though, since part of that is "categorizing" the changes, I think we need to divy up the distribution before changing what we now do for release note changes. Personally, I'd like to prioritize moving the build over to Maven, and dividing the distribution into multiple artifacts with their own release cycles, so that we start taking advantage of features like this. -Ted. On Fri, 27 Feb 2004 08:10:53 -0600, Joe Germuska wrote: > At 9:05 AM +0100 2/27/04, nicolas De Loof wrote: >> Can you please post a "what's new" about this release to help me >> make my boss agree to use Struts 1.2.0 for new projects ? >> > > Are committers familiar with the Maven changes.xml file/plugin? If > it exists, it can be used to generate something that looks like > this: > > http://maven.apache.org/changes-report.html > > > Even though Maven isn't our primary build mechanism, using > changes.xml might be a good way to track what we're doing. I hope > I'm not embarassing myself, but there isn't any basic change log > already is there? If so, I sure haven't been tracking it. > > I guess putting every single commit into the changes.xml file isn't > appropriate, or the thing would get huge. Also, Maven can generate > a separate report for that (http://maven.apache.org/changelog- > report.html) > > Since changes.xml is structured, we could probably come up with a > transform to use it in the current Ant-built documentation until we > are using Maven, and if nothing else, it provides a single place to > log things.> > Of course, if people don't think it's worth the energy, I'd rather > leave it out than have it there but inaccurate. > > Joe > > > PS an example of the XML syntax is here: > http://maven.apache.org/reference/plugins/changes/ It's about as > much doc as I've ever seen for it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
