On Tue, Oct 28, 2008 at 1:11 PM, Allison Randal <[EMAIL PROTECTED]> wrote: > We are now the proud owners of: > > ftp://ftp.parrot.org/pub/parrot/
Yay. > soon-to-be the home of Parrot release tarballs, OS packages, and > potentially also Parrot modules. And language releases. =-) > So, how do we want to structure the ftp directories? A few things we > need to support or may want to consider: > > - A directory for each release, to contain the tarballs and packages for > that release. +1 > - A clear path (alias) to the *current* release, that's always the same. Perhaps current -> devel before 1.0 and -> stable after? > - Directories for 'stable' and 'devel'? > > - A top-level directory 'releases' to make room for subdivisions for > modules, etc? So, - pub/parrot/releases/0.8.0 - pub/parrot/releases/devel -> pub/parrot/releases/0.8.0 - pub/parrot/releases/current -> pub/parrot/releases/devel with pub/parrot/... languages? modules, etc? > > Ubuntu's releases directory is a good example: > > ftp://ftp.parrot.org/pub/ubuntu-releases/ > > You'll find a few bad examples if you poke around in pub/. > > Any thoughts/comments? > > Allison > > _______________________________________________ > http://lists.parrot.org/mailman/listinfo/parrot-dev > -- Will "Coke" Coleda _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
