commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Yandell <flame...@gmail.com>
Subject Re: [lang] release strategy
Date Sun, 13 Feb 2005 19:33:29 GMT
In the long term, yeah. In the short term I'll just do this the old way :)

Hen

On Sun, 13 Feb 2005 10:50:32 -0500, Phil Steitz <phil@steitz.com> wrote:
> I get it now -- both points.  Need to think about how to separate the
> docs site gen.
> 
> Phil
> 
> Henri Yandell wrote:
> >
> > On this particular issue, I think the documentation should be included
> > with the build and not the site. Even more importantly for Collections
> > than for Lang; a Collections 2.1 downloader should not get lots of
> > Collections 3.0 stuff.
> >
> > We don't separate documentation and site though, so I'm -0 for the
> > xdocs being in there and will add them in, it just changes the release
> > strategy.
> >
> >
> >>I don't see this as a big maintenance issue, but could be I am missing
> >>Hen's point below.
> >
> >
> > If we branch off and do a release from a branch, we have to maintain
> > the branch's site for the release and the trunk's site for our live
> > site. So our previous release strategy makes more sense under this
> > scenario, release from trunk and then tag at the release point.
> >
> > Hen
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message