t additions to the FAQ or status updates in that case
then?
> Update the main site or only the new one?
>
> > -Original Message-
> > From: Eric Pugh [mailto:[EMAIL PROTECTED]
> > Sent: Monday, 25 August 2003 9:49 AM
> > To: 'Maven Developers List
On Sun, 2003-08-24 at 20:46, Brett Porter wrote:
> Where do we put additions to the FAQ or status updates in that case then?
> Update the main site or only the new one?
The latest news goes on the most recently generated site. So it might
become the norm that status document in the released site p
HI Brett,
FYI, in Cactus land, I've used option 5). See
http://jakarta.apache.org/cactus. You'll see there is a link to the
newest stuff in the top right corner of the page.
We tried 4) but it didn't work as users expect to see the doc for the
released version on the main web site page.
We also
On second thoughts, I'm ok with us having the release as the major site,
as long as there is a directory there for HEAD in xdocs.
Similar to what's in
http://maven.apache.org/reference/developers/releasing-plugins.html
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/pe
Jason van Zyl <[EMAIL PROTECTED]> wrote on 25/08/2003 11:09:55 AM:
> On Sun, 2003-08-24 at 18:42, Brett Porter wrote:
> > Hi,
> >
> > I wanted to bounce around ideas about how we generate the site at
> > maven.apache.org. I fielded a question from a user on the dev list who
was
> > trying to use
Where do we put additions to the FAQ or status updates in that case then?
Update the main site or only the new one?
> -Original Message-
> From: Eric Pugh [mailto:[EMAIL PROTECTED]
> Sent: Monday, 25 August 2003 9:49 AM
> To: 'Maven Developers List'
> Subje
On Sun, 2003-08-24 at 18:42, Brett Porter wrote:
> Hi,
>
> I wanted to bounce around ideas about how we generate the site at
> maven.apache.org. I fielded a question from a user on the dev list who was
> trying to use installation instructions for the next release for installing
> beta-10. Fair e
I think I like #4. The reason is that once a 1.0 goes out, most users will
only be wanting to look at the documentation that applies to that release.
By having a prominent link to "whats current" then for people who are using
unreleased versions will be able to look at the docs that apply to CVS h
