commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <>
Subject Re: [compress] Two issues with releasing the release
Date Sat, 23 May 2009 10:41:57 GMT
On 23/05/2009, Christian Grobmeier <> wrote:
> >> Next dev. snapshot is 1.1.
>  >
>  > One has to wonder why we put the version number on the site :) It's
>  > completely meaningless and just leads to confusion.
>  >
>  > I think it dates in Maven from the notion that your site would be your
>  > documentation. However websites serve a completely different purpose
>  > from documentation so that died as an idea.
>  >
>  > We should stop including the version on the websites.

The web-sites still contain important information that is not readily
available elsewhere, some of which is also version dependent. If the
website always relates to the current SVN trunk, then that information
can be incorrect for the current release.

> I agree. I am also thining that a website can be deployed more often
>  than the artifacts are. What if I have new examples or new, in depths
>  tutorials? Do I have to wait till a next release?

There are some that say that one should do another release with the
updated information, but given that checking releases is
time-consuming I don't think that's appropriate.

>  Decoupling artifact releasing and site releasing could help

Agreed, but there are other ways to do this, for example using a
branch for the documentation and releasing from that.

>  Christian
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail:
>  For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message