On Sun, 22 Feb 2004 22:38:24 -0800 (PST), Martin Cooper wrote: > Actually, with this new release strategy, where should the > announcement message go, since it's not a Final release? The same > lists, or a subset? Thoughts?
Following Craig's description of the Tomcat release approach (copy below), I'd say we should make an announcement to the Struts DEV and USER lists, with an URL leading to one of our home directories (or wherever Tomcat and others have been posting such things), but not the Jakarta announcement list. I imagine we'd now reserve the latter for a General Availability release that's being mirrored. Sorry if the taglib-exercise module is flaky. If it is, mea culpa. But once it's up there, we can still announce it, see if there is anything else we can fix, and then try again with 1.2.1. That would also give us a chance to apply that license patch. -Ted. On Tue, 16 Dec 2003 11:27:45 -0800, Craig R. McClanahan wrote: > The Tomcat folks do indeed vote on every release -- they just do > things in a little different order: > > * Post what amounts to a release candidate and > announce to a limited audience (dev and user > lists) asking for testing. > > * Testing ensues ... > > * Call a vote on the release, with the options > to call it alpha, beta, stable (that's fine > with me), or withdraw (if there was some > bad problem). > > * Announce to the world and do the usual process > of distributing the bits. > > The same approach would work for us, and IMHO meets the Jakarta > requirements with one additional wrinkle -- the Jakarta PMC needs > the opportunity to vote on releases as well, to be consistent with > the current ASF reqirements. On Sun, 22 Feb 2004 22:38:24 -0800 (PST), Martin Cooper wrote: > The release is built, but I have a couple of problems. > > > 1) My ISP has gone flaky on me, and I haven't been able to upload > it to minotaur. They claim the problems should be fixed tomorrow, > so hopefully I'll be able to upload it then. > > 2) Some of the exercise-taglibs tests are failing: > 2a) <bean:include> fails because it is trying to include > welcome.html, but there is no such file. > 2b) <html:img> fails because there are no images in the struts- > examples web app at all. > 2c) <html:messages> fails with a lot of nulls in the test table. > > > It looks like all of these are probably issues with the test app > itself, rather than the tags, so I'm not overly concerned, and > suspect we probably should go ahead with 1.2.0 anyway, especially > since we're not claiming it's a final release. > > Once I get the build uploaded, I'll ask other folks to take it for > a spin before sending out an announcement. > > Actually, with this new release strategy, where should the > announcement message go, since it's not a Final release? The same > lists, or a subset? Thoughts? > > -- > Martin Cooper --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
