commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: [LANG] Snap-shot version in website header
Date Sat, 04 Jan 2014 15:19:35 GMT
On 4 January 2014 08:29, Henri Yandell <flamefew@gmail.com> wrote:
> To Sebb and Bendikt:
>
> I'm ambivalent on whether the reports are release version or snapshot, I
> can see value in both (one encourages users, the other contributors).
> However the site _has_ to be trunk. Having to do a new release just so we
> can update the site doesn't strike me as healthy.

A new release is *not* necessary.

As already explained, in JMeter we create the initial website from the tag.
If we need to make changes subsequently, we create a documentation
branch from the tag and update that.
This allows the website to keep track with the current release even if
we have made changes to the trunk docs.

It's not all that often that changes need to be made to the site, so
this is not a big deal.

The alternative is to have a trunk site which includes subsites for
one or more releases
However this can lead to problems with relative links as was found for Codec.
If we can solve that, then it would be good for components that have
multiple active release versions.

> To Gary:
>
> It has two versions (source version and the generated version checked in),
> but there's no reason either should be shown so prominently, if at all.
>
> Hen
>
>
> On Fri, Jan 3, 2014 at 6:20 AM, Gary Gregory <garydgregory@gmail.com> wrote:
>
>> But the site is versioned, in SVN and as a reflection of the SVN/release
>> of the code base.
>>
>> G
>>
>> -------- Original message --------
>> From: Benedikt Ritter <britter@apache.org>
>> Date:01/03/2014  08:12  (GMT-05:00)
>> To: Commons Developers List <dev@commons.apache.org>
>> Subject: Re: [LANG] Snap-shot version in website header
>>
>> 2014/1/3 Henri Yandell <flamefew@gmail.com>
>>
>> > Yes we change the site between releases.
>> >
>> > The bigger question is why we have a version number on the website, it
>> > isn't versioned.
>> >
>>
>> Well at least the repots have kind of a version, because they reflect the
>> state of the code they were build against.
>> And to me the reports for the latest release are far more important then
>> those for the current trunk.
>>
>>
>> >
>> > Hen
>> >
>> >
>> > On Thu, Jan 2, 2014 at 6:45 AM, Duncan Jones <duncan@wortharead.com>
>> > wrote:
>> >
>> > > Hi all,
>> > >
>> > > The top of the commons-lang web page reads:
>> > >
>> > > "Last Published: 01 January 2014  | Version: 3.3-SNAPSHOT "
>> > >
>> > > Shouldn't that read:
>> > >
>> > > "Last Published: 01 January 2014  | Version: 3.2 " ??
>> > >
>> > > Or are we changing the site between releases, thus necessitating that
>> > > we build a site using the current (snapshot) version number?
>> > >
>> > > Thanks,
>> > >
>> > > Duncan
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> > > For additional commands, e-mail: dev-help@commons.apache.org
>> > >
>> > >
>> >
>>
>>
>>
>> --
>> http://people.apache.org/~britter/
>> http://www.systemoutprintln.de/
>> http://twitter.com/BenediktRitter
>> http://github.com/britter
>>

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


Mime
View raw message