Quoting Joe Germuska <[EMAIL PROTECTED]>: > At 2:48 PM -0500 3/14/04, Ted Husted wrote: > >I'd say we could branch what we have as 1.2 and start thinking of > >the HEAD as 1.3. > > > >IMHO, the quickest way to sort out what we need to do with the > >Struts-Chain RequestProcessor is to get it out there as the nightly > >build. [Many hands make light work ;)] > > > >So, we could reserve the 1.2 for any desperate fixes (as we've done > >before), but do anything resembling new development against the HEAD > >(1.3). > > I might do something like this over the weekend, depending on my time > (then again, I may not at all!) > > But if I did, I'd want to see if anyone had any strong feelings, or > fixes they thought they'd like to get in before a branch, or... ? > > Or should all of this wait until we get the move to struts.apache.org > settled? I'm assuming we'll reorganize CVS as part of that, into > struts-core, struts-taglib, etc...
I think there's a lot of merit in rationalizing the directory structures as part of the move to TLP-ness. > Speaking of that, can we/should > we do anything to preserve CVS logs if we move files? Or will we > start fresh? I think if we move the actual CVS files it will all be > preserved, but I've never tried that. > There are ways to preserve history, but I suspect there will be difficulties if we decide to split up what has been a single repository (jakarta-struts) into per-subpackage repositories. A guru on CVS would definitely be useful here. > I'm interested in getting the Struts Chain stuff mainstreamed, but > like I said, this may very well not be the weekend I start on it. In > any case, I figured a branch would be cause for a little bit of > discussion amongst committers. > I'm going to focus some energy as well on commons-chain and struts-chain now that JavaServer Faces is done. > Joe Craig --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
