river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frank Barnaby <Frank.Barn...@Sun.COM>
Subject Layout for River Distribution Site
Date Thu, 03 Jan 2008 02:54:41 GMT
I'm putting together the layout for the River distribution site.  I'd
like to start with a simple layout for the AR1 release but structure
it to accommodate future releases.  Here's the proposed layout,
which is based on portions of existing projects:


   HEADER.html
   KEYS -> binaries/2.1.1/KEYS
   README.html

   apache-river-2.1.1-incubating-bin.zip -> binaries/2.1.1/apache- 
river-2.1.1-incubating-bin.zip
   apache-river-2.1.1-incubating-bin.zip.asc -> binaries/2.1.1/apache- 
river-2.1.1-incubating-bin.zip.asc
   apache-river-2.1.1-incubating-bin.zip.md5 -> binaries/2.1.1/apache- 
river-2.1.1-incubating-bin.zip.md5
   apache-river-2.1.1-incubating-bin.zip.sha -> binaries/2.1.1/apache- 
river-2.1.1-incubating-bin.zip.sha

   apache-river-2.1.1-incubating-src.zip -> source/2.1.1/apache- 
river-2.1.1-incubating-src.zip
   apache-river-2.1.1-incubating-src.zip.asc -> source/2.1.1/apache- 
river-2.1.1-incubating-src.zip.asc
   apache-river-2.1.1-incubating-src.zip.md5 -> source/2.1.1/apache- 
river-2.1.1-incubating-src.zip.md5
   apache-river-2.1.1-incubating-src.zip.sha -> source/2.1.1/apache- 
river-2.1.1-incubating-src.zip.sha

   binaries/2.1.1/KEYS
   binaries/2.1.1/apache-river-2.1.1-incubating-bin.zip
   binaries/2.1.1/apache-river-2.1.1-incubating-bin.zip.asc
   binaries/2.1.1/apache-river-2.1.1-incubating-bin.zip.md5
   binaries/2.1.1/apache-river-2.1.1-incubating-bin.zip.sha

   source/2.1.1/KEYS -> ../../binaries/2.1.1/KEYS
   source/2.1.1/apache-river-2.1.1-incubating-src.zip
   source/2.1.1/apache-river-2.1.1-incubating-src.zip.asc
   source/2.1.1/apache-river-2.1.1-incubating-src.zip.md5
   source/2.1.1/apache-river-2.1.1-incubating-src.zip.sha


The release-management guide (http://incubator.apache.org/guides/releasemanagement.html 
)
suggests that the latest binaries are often linked at the top level
to allow users to easily locate the latest downloads.  Other, well
known projects (eg, ant and httpd) use a layout similar to what I've
proposed here.  Note that Apache does not have a required layout, but
they do suggest that existing structures be studied before creating
one.

The README.html file would contain project specific information related
to the download site.  The httpd server automatically appends the readme
content to the directory-index page.  Alternatively, we could use the
HEADER.html file to have content prepended to the directory-index page,
or we could use a combination of both.  Httpd, for example, uses the
header for an index into the appended readme:

   http://www.apache.org/dist/httpd

The Ant project has a slightly different configuration:

   http://www.apache.org/dist/ant

I've created basic HEADER.html and README.html files that will need to
be filled in.  I don't see a need for an index in the header at this
time, but the option is there when we decide to use it.

I've already created the basic web site at:

   http://www.apache.org/dist/incubator/river

which is group writable and is located on people.apache.org at:

   /www/www.apache.org/dist/incubator/river

Apache seems to have some automatic publishing mechanism that is run on
some periodic schedule, so the River page is a bit out of date at the
moment.  I'm hoping that it will be updated within the next hour or two.

All comments and suggestions are welcome.



Frank

Mime
View raw message