You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Karl Heinz Marbaise <kh...@gmx.de> on 2010/02/27 18:50:52 UTC
Web-Site: Linking to CHANGES file for different releases
Hi,
i have question about the links in different release-notes for different
release to the CHANGES file.
At the moment all release note files (1.1. to 1.6.html) will link to the
CHANGES file from trunk of Subversion....
Wouldn't it be better, based on historical reference to link to the
CHANGES file into the appropriate release e.g.
1.1.html should reference .../repos/asf/subversion/tags/1.1.0/CHANGES
1.2.html should reference .../repos/asf/subversion/tags/1.2.0/CHANGES
...
and so on..
What do you think ?
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
Re: Web-Site: Linking to CHANGES file for different releases
Posted by "C. Michael Pilato" <cm...@collab.net>.
I'm game.
And Karl, I hereby state my approval for you to go ahead and commit these
website related fixes and any other broken-link fixes you wish to commit in
the coming days. I've only seen one thing in your past N patches that I
would have done differently, so let's just cut out the middle man, shall we?
Karl Heinz Marbaise wrote:
> sorry...not answered to the list.
>
>> Hi Michael,
>>
>>
>>> Yeah, the great thing about always pointing at trunk is that it
>>> contains all
>>> the change records, so if you want to see what happened in other
>>> releases,
>>> the info is readily available.
>>>
>>> The bad thing is that it contains all the change records, so if you
>>> don't
>>> want to see what happened in other releases, you gotta dig some for the
>>> release you do care about.
>> Yes...that's a point...
>>>
>>> But here's my case for *not* linking against the tagged CHANGES
>>> items: we
>>> only push out new release notes for big X.Y.0 releases, yet folks
>>> refer to
>>> them as an explanation of what they are getting with any installation of
>>> Subversion from the X.Y lineage. It would be weird to download
>>> Subversion
>>> 1.6.9, read the 1.6 release notes, and then get pointed to a quite-stale
>>> 1.6.0 CHANGES list. So if we're going to do anything around these
>>> parts, we
>>> should be pointing to the CHANGES files as they exist in the release
>>> *branches* (e.g. branches/1.6.x/CHANGES).
>> That's a better solution for this...
>>
>> I would vote for that ...
>>
>> +1 from me...
>>
>>
>> Kind regards
>> Karl Heinz Marbaise
>
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Re: Web-Site: Linking to CHANGES file for different releases
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
sorry...not answered to the list.
> Hi Michael,
>
>
>> Yeah, the great thing about always pointing at trunk is that it
>> contains all
>> the change records, so if you want to see what happened in other
>> releases,
>> the info is readily available.
>>
>> The bad thing is that it contains all the change records, so if you don't
>> want to see what happened in other releases, you gotta dig some for the
>> release you do care about.
> Yes...that's a point...
>>
>> But here's my case for *not* linking against the tagged CHANGES
>> items: we
>> only push out new release notes for big X.Y.0 releases, yet folks
>> refer to
>> them as an explanation of what they are getting with any installation of
>> Subversion from the X.Y lineage. It would be weird to download
>> Subversion
>> 1.6.9, read the 1.6 release notes, and then get pointed to a quite-stale
>> 1.6.0 CHANGES list. So if we're going to do anything around these
>> parts, we
>> should be pointing to the CHANGES files as they exist in the release
>> *branches* (e.g. branches/1.6.x/CHANGES).
> That's a better solution for this...
>
> I would vote for that ...
>
> +1 from me...
>
>
> Kind regards
> Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
Re: Web-Site: Linking to CHANGES file for different releases
Posted by "C. Michael Pilato" <cm...@collab.net>.
Neels J Hofmeyr wrote:
> Neels J Hofmeyr wrote:
>> Karl Heinz Marbaise wrote:
>>> Wouldn't it be better, based on historical reference to link to the
>>> CHANGES file into the appropriate release e.g.
>>>
>>> 1.1.html should reference .../repos/asf/subversion/tags/1.1.0/CHANGES
>>> 1.2.html should reference .../repos/asf/subversion/tags/1.2.0/CHANGES
>> (IOW make the 'CHANGES' link in site/publish/docs/release-notes/1.*.html
>> point at tags/1.*.0/CHANGES instead of trunk/CHANGES.)
[...]
> The trunk/CHANGES does include all versions' changes. Still, it would be
> good to not link to the collab.net repos anymore. (At least 1.1.html does that.)
Yeah, the great thing about always pointing at trunk is that it contains all
the change records, so if you want to see what happened in other releases,
the info is readily available.
The bad thing is that it contains all the change records, so if you don't
want to see what happened in other releases, you gotta dig some for the
release you do care about.
But here's my case for *not* linking against the tagged CHANGES items: we
only push out new release notes for big X.Y.0 releases, yet folks refer to
them as an explanation of what they are getting with any installation of
Subversion from the X.Y lineage. It would be weird to download Subversion
1.6.9, read the 1.6 release notes, and then get pointed to a quite-stale
1.6.0 CHANGES list. So if we're going to do anything around these parts, we
should be pointing to the CHANGES files as they exist in the release
*branches* (e.g. branches/1.6.x/CHANGES).
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Re: Web-Site: Linking to CHANGES file for different releases
Posted by Neels J Hofmeyr <ne...@elego.de>.
Neels J Hofmeyr wrote:
> Karl Heinz Marbaise wrote:
>> Hi,
>>
>> i have question about the links in different release-notes for different
>> release to the CHANGES file.
>> At the moment all release note files (1.1. to 1.6.html) will link to the
>> CHANGES file from trunk of Subversion....
>>
>> Wouldn't it be better, based on historical reference to link to the
>> CHANGES file into the appropriate release e.g.
>>
>> 1.1.html should reference .../repos/asf/subversion/tags/1.1.0/CHANGES
>> 1.2.html should reference .../repos/asf/subversion/tags/1.2.0/CHANGES
> (IOW make the 'CHANGES' link in site/publish/docs/release-notes/1.*.html
> point at tags/1.*.0/CHANGES instead of trunk/CHANGES.)
>
> +1
Sorry, too quick there. Make that a
-0
The trunk/CHANGES does include all versions' changes. Still, it would be
good to not link to the collab.net repos anymore. (At least 1.1.html does that.)
~Neels
Re: Web-Site: Linking to CHANGES file for different releases
Posted by Neels J Hofmeyr <ne...@elego.de>.
Karl Heinz Marbaise wrote:
> Hi,
>
> i have question about the links in different release-notes for different
> release to the CHANGES file.
> At the moment all release note files (1.1. to 1.6.html) will link to the
> CHANGES file from trunk of Subversion....
>
> Wouldn't it be better, based on historical reference to link to the
> CHANGES file into the appropriate release e.g.
>
> 1.1.html should reference .../repos/asf/subversion/tags/1.1.0/CHANGES
> 1.2.html should reference .../repos/asf/subversion/tags/1.2.0/CHANGES
(IOW make the 'CHANGES' link in site/publish/docs/release-notes/1.*.html
point at tags/1.*.0/CHANGES instead of trunk/CHANGES.)
+1
~Neels