Craig, Some ideas for tracking dependant components...
I must admit to some confusion about what version of the jakarta-commons and other components to use with the nightly struts builds because (1) sometimes the last release of the dependent component no longer works with the struts or (2) the latest nightly build of the dependent component either does not work or is considered too experimental to use. Would it be beneficial for everyone if we determined the what version (or build #/date) of the dependant components was the one to use with each nightly build? I know that there is some online documentation to this effect, but it doesn't appear that this is updated except at major releases. Am I wrong in asserting that this documentation is not correct for the latest nightly build? Also, seems to me that labeling the component depended upon (jakarta-commons) is backwards. Shouldn't we just document in jakarta-struts the version (or build #/date) of each component used? Are the nightly builds of these components already automatically tagged in CVS for quick recoverly? Sincerely, James. -----Original Message----- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Monday, March 18, 2002 9:24 AM To: Struts Developers List Subject: Re: Beta 1 update +1, but if you can wait until after midnight (Pacific Time) tonight, I'll be able to get some more bug fixes done. I also did some fixes/enhancements in commons-beanutils over the weekend, which raises a point -- it would also be good to tag the specific bits of the Commons packages that you include in the beta with the same tag. Since Martin has commit access on jakarta-commons, this shouldn't be a problem. And, nobody should complain since CVS doesn't give a rip how many tags there are (just don't create branch tags). Craig On Sun, 17 Mar 2002, Martin Cooper wrote: > Date: Sun, 17 Mar 2002 21:41:22 -0800 > From: Martin Cooper <[EMAIL PROTECTED]> > Reply-To: Struts Developers List <[EMAIL PROTECTED]> > To: Struts Developers List <[EMAIL PROTECTED]> > Subject: Beta 1 update > > First of all, I sincerely apologise to you all for the length of time it is > taking to get Beta 1 out the door. Unfortunately, I managed to get sick, and > still haven't quite got back to full strength yet. > > A few things have happened since I tagged the CVS tree for Beta 1. > > 1) Craig has made a boatload of bug fixes to the code base. > > 2) Arron made some changes to the nested taglib which he requested be > included in Beta 1. > > 3) David made many changes to Validator and the way it hooks into Struts. He > also updated some of the files in CVS to tag them as part of Beta 1. > > 4) Rob is checking in UML diagrams as I write this. > > Given these changes, and especially given the already-updated tags in CVS, I > think it would make sense at this point to retag the entire tree to pick up > the latest of everything as Beta 1. This would give us a better, stronger, > first beta. I promise to complete the beta release process in one phase this > time, to avoid a repeat of the current situation. > > Is everyone OK with this approach? > > -- > Martin Cooper > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
