[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: s.a.o/download/ vs. s.a.o/source-code.html

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Fri, 10 Jun 2011 19:55:27 +0300

Hyrum K Wright wrote on Fri, Jun 10, 2011 at 11:13:16 -0500:
> On Fri, Jun 10, 2011 at 10:40 AM, C. Michael Pilato <cmpilato_at_collab.net> wrote:
> > On 06/10/2011 09:40 AM, Hyrum K Wright wrote:
> >> In getting ready for the 1.7.0 release cycle, we've put together a new
> >> download page on subversion.apache.org.  This page allows us to make
> >> use of the Apache mirroring infrastructure when distributing new
> >> releases.
> >>
> >> My aim is to have the download page eventually become the canonical
> >> source for releases, replacing source-code.html (from which it has
> >> largely copied content).  I've got some rudimentary content on that
> >> page, and will be directing people there in the course of announcing
> >> the alpha releases, but would appreciate additional eyes.
> >
> > I like it.  I think I would change "Supported release" to "Supported
> > release(s)", and include in the section text an explicit mention of 1.6.17.
> >  That might seem redundant in light of the section above it naming 1.6.17 as
> > the latest release, but for someone navigating via a shared link to
> > http://subversion.apache.org/download/#supported-release, they won't
> > necessarily see that bit above.
> >
> > I'll make this change myself right now.
> Thanks! I've got a few more thoughts I'm throwing out here (for
> nobody in particular).
> I think there are really two audiences here: people downloading
> releases, and folks looking to get the source from the repo. I'd like
> to make /download/ the landing page for the first group, and have it
> *dirt simple* for them to do what they came for, namely download a
> Subversion release. As it is, with instructions on how to check stuff
> out and caveats about nightly builds and such, the page feels too
> busy, and I'm concerned folks will get lost.
> So I'd propose we keep source-code.html as the "how to checkout our
> code and build from such a working copy", and /download/ as "how to
> get a release". I'm not in a position to actually effect this change
> for bit, but I'll eventually get around to it if nobody else does.

While at it, why not move the 'nightly releases' bit to the source-code page?

They are far closer to trunk than to any other thing we call 'release'
(alphas included).

> -Hyrum
Received on 2011-06-10 18:56:18 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.