You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Steve Peterson <st...@zpfe.com> on 2003/07/22 14:39:38 UTC
Re: Building struts-legacy (was: Re: Nightly build is
generating empty binary distribution file)
While you are talking about updating the build, another small item for the
todo list would be to sync the version number assignment up with the
now-project-standard a.b.c style release numbering. I have personally seen
some (small) confusion related to release 1.1.0 being stored in
jakarta-struts-1.1.zip.
S
At 08:14 AM 7/22/2003 -0400, Ted Husted wrote:
>Craig R. McClanahan wrote:
>>Do we really want to wait that long? CAN we wait that long?
>
>How long is a piece of String. =:0)
>
>We can do a 1.2 release candidate this month, and then figure on doing 1.3
>by the end of August.
>
>As long as week keep 1.x.x in evolutionary mode, I don't think we need to
>worry too much about maintaining branch for 1.#.x versus 1.#.x. In
>practice, the 1.1 branch has been out-there for over a year, and it seems
>unlikely that any serious problems could be cured with a trivial
>point-release fix. We just have to be careful to keep the HEAD
>release-ready and whiteboard anything radical before merging it in.
>
>I have family coming in this week and can't volunteer to roll 1.2 myself
>this weekend. But if no one beats me to it, I'd like to roll a 1.2 release
>candidate the first weekend in August.
>
>-Ted.
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: struts-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org
Re: Building struts-legacy (was: Re: Nightly build is generating empty binary distribution file)
Posted by Martin Cooper <ma...@apache.org>.
"David Graham" <gr...@yahoo.com> wrote in message
news:20030723170600.21229.qmail@web20707.mail.yahoo.com...
> --- Martin Cooper <ma...@apache.org> wrote:
> >
> > "Steve Peterson" <st...@zpfe.com> wrote in message
> > news:5.2.0.9.0.20030722073711.038b8be0@wheresmymailserver.com...
> > > While you are talking about updating the build, another small item for
> > the
> > > todo list would be to sync the version number assignment up with the
> > > now-project-standard a.b.c style release numbering. I have personally
> > seen
> > > some (small) confusion related to release 1.1.0 being stored in
> > > jakarta-struts-1.1.zip.
> >
> > The problem here, I think, is that we should not be referring to it as
> > 1.1.0
> > at all. The decision we made, unless I'm mistaken, is that we would
> > start to
> > use the 3-part numbering *after* Struts 1.1, not *with* Struts 1.1. So
> > there
> > is no 1.1.0 release.
>
> I'm a bit confused by this. Didn't we already have a 3 part numbering
> system with 1.0.1 and 1.0.2? 1.1.1 would be a bugfix release only;
> however, we decided to not do that and roll up any bug fixes +
> enhancements into 1.2.0.
We had three-part numbering, yes, but only for bug fix releases. But we had
1.0 and 1.1 for the regular releases, not 1.0.0 and 1.1.0. Going forward
from now, the plan is to always have three parts to the release number, even
for non-bug-fix-only releases, in a similar manner to Tomcat.
--
Martin Cooper
>
> David
>
> >
> > --
> > Martin Cooper
> >
> >
> > >
> > > S
> > >
> > > At 08:14 AM 7/22/2003 -0400, Ted Husted wrote:
> > > >Craig R. McClanahan wrote:
> > > >>Do we really want to wait that long? CAN we wait that long?
> > > >
> > > >How long is a piece of String. =:0)
> > > >
> > > >We can do a 1.2 release candidate this month, and then figure on
> > doing
> > 1.3
> > > >by the end of August.
> > > >
> > > >As long as week keep 1.x.x in evolutionary mode, I don't think we
> > need to
> > > >worry too much about maintaining branch for 1.#.x versus 1.#.x. In
> > > >practice, the 1.1 branch has been out-there for over a year, and it
> > seems
> > > >unlikely that any serious problems could be cured with a trivial
> > > >point-release fix. We just have to be careful to keep the HEAD
> > > >release-ready and whiteboard anything radical before merging it in.
> > > >
> > > >I have family coming in this week and can't volunteer to roll 1.2
> > myself
> > > >this weekend. But if no one beats me to it, I'd like to roll a 1.2
> > release
> > > >candidate the first weekend in August.
> > > >
> > > >-Ted.
> > > >
> > > >
> > > >
> > > >
> > > >---------------------------------------------------------------------
> > > >To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
> > > >For additional commands, e-mail: struts-dev-help@jakarta.apache.org
> > > >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: struts-dev-help@jakarta.apache.org
> >
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org
Re: Building struts-legacy (was: Re: Nightly build is generating empty binary distribution file)
Posted by David Graham <gr...@yahoo.com>.
--- Martin Cooper <ma...@apache.org> wrote:
>
> "Steve Peterson" <st...@zpfe.com> wrote in message
> news:5.2.0.9.0.20030722073711.038b8be0@wheresmymailserver.com...
> > While you are talking about updating the build, another small item for
> the
> > todo list would be to sync the version number assignment up with the
> > now-project-standard a.b.c style release numbering. I have personally
> seen
> > some (small) confusion related to release 1.1.0 being stored in
> > jakarta-struts-1.1.zip.
>
> The problem here, I think, is that we should not be referring to it as
> 1.1.0
> at all. The decision we made, unless I'm mistaken, is that we would
> start to
> use the 3-part numbering *after* Struts 1.1, not *with* Struts 1.1. So
> there
> is no 1.1.0 release.
I'm a bit confused by this. Didn't we already have a 3 part numbering
system with 1.0.1 and 1.0.2? 1.1.1 would be a bugfix release only;
however, we decided to not do that and roll up any bug fixes +
enhancements into 1.2.0.
David
>
> --
> Martin Cooper
>
>
> >
> > S
> >
> > At 08:14 AM 7/22/2003 -0400, Ted Husted wrote:
> > >Craig R. McClanahan wrote:
> > >>Do we really want to wait that long? CAN we wait that long?
> > >
> > >How long is a piece of String. =:0)
> > >
> > >We can do a 1.2 release candidate this month, and then figure on
> doing
> 1.3
> > >by the end of August.
> > >
> > >As long as week keep 1.x.x in evolutionary mode, I don't think we
> need to
> > >worry too much about maintaining branch for 1.#.x versus 1.#.x. In
> > >practice, the 1.1 branch has been out-there for over a year, and it
> seems
> > >unlikely that any serious problems could be cured with a trivial
> > >point-release fix. We just have to be careful to keep the HEAD
> > >release-ready and whiteboard anything radical before merging it in.
> > >
> > >I have family coming in this week and can't volunteer to roll 1.2
> myself
> > >this weekend. But if no one beats me to it, I'd like to roll a 1.2
> release
> > >candidate the first weekend in August.
> > >
> > >-Ted.
> > >
> > >
> > >
> > >
> > >---------------------------------------------------------------------
> > >To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
> > >For additional commands, e-mail: struts-dev-help@jakarta.apache.org
> > >
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-dev-help@jakarta.apache.org
>
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org
Re: Building struts-legacy (was: Re: Nightly build is generating empty binary distribution file)
Posted by Martin Cooper <ma...@apache.org>.
"Steve Peterson" <st...@zpfe.com> wrote in message
news:5.2.0.9.0.20030722073711.038b8be0@wheresmymailserver.com...
> While you are talking about updating the build, another small item for the
> todo list would be to sync the version number assignment up with the
> now-project-standard a.b.c style release numbering. I have personally
seen
> some (small) confusion related to release 1.1.0 being stored in
> jakarta-struts-1.1.zip.
The problem here, I think, is that we should not be referring to it as 1.1.0
at all. The decision we made, unless I'm mistaken, is that we would start to
use the 3-part numbering *after* Struts 1.1, not *with* Struts 1.1. So there
is no 1.1.0 release.
--
Martin Cooper
>
> S
>
> At 08:14 AM 7/22/2003 -0400, Ted Husted wrote:
> >Craig R. McClanahan wrote:
> >>Do we really want to wait that long? CAN we wait that long?
> >
> >How long is a piece of String. =:0)
> >
> >We can do a 1.2 release candidate this month, and then figure on doing
1.3
> >by the end of August.
> >
> >As long as week keep 1.x.x in evolutionary mode, I don't think we need to
> >worry too much about maintaining branch for 1.#.x versus 1.#.x. In
> >practice, the 1.1 branch has been out-there for over a year, and it seems
> >unlikely that any serious problems could be cured with a trivial
> >point-release fix. We just have to be careful to keep the HEAD
> >release-ready and whiteboard anything radical before merging it in.
> >
> >I have family coming in this week and can't volunteer to roll 1.2 myself
> >this weekend. But if no one beats me to it, I'd like to roll a 1.2
release
> >candidate the first weekend in August.
> >
> >-Ted.
> >
> >
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: struts-dev-help@jakarta.apache.org
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org