Parrot FTP site

[Allison Randal]

We are now the proud owners of:

   ftp://ftp.parrot.org/pub/parrot/

soon-to-be the home of Parrot release tarballs, OS packages, and 
potentially also Parrot modules.

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.

- A clear path (alias) to the *current* release, that's always the same.

- Directories for 'stable' and 'devel'?

- A top-level directory 'releases' to make room for subdivisions for 
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