Layout of subproject distro downloads on people.apache.org

[kelvin goodson <ke...@gmail.com>]

Now that Java SDO has met the criteria for releasing I was about to post my
distributions somewhere under
http://people.apache.org/dist/incubator/tuscany/

Changes in our project structure, and a little lack of foresight in our
early placement of releases make this not a very clear cut task.
Currently it has a structure of

- incubating-M1
    - <java release archives>
- cpp
   - incubating-M1
      - linux
          <archives>
      - windows
          <archives>
   -1.0-incubator-M2
      - linux
          <archives>
      - windows
          <archives>


So, one question is ... are we bound to not breaking old published URLs,  or
are we OK if we rearrange this hierarchy and the tuscany website downloads
page in synchrony?

Whether or not we can rearrange the existing state, there is the question of
how we proceed with holding new releases.  We have 3 (or in the C++ case 4)
orthogonal concepts to arrange into a hierarchy (language, release,
subproject,  with C++ also having platform).

I propose that we arrange the hierarchy in the sequence -- language,
release, subproject (platform).

Regards, Kelvin.

Re: Layout of subproject distro downloads on people.apache.org

[kelvin goodson <ke...@thegoodsons.org.uk>]

> I think that this will run into problems as we start to release
>  modules independently of each other.
...
> This is very similar ot the layout Maven uses for its repo - perhaps
> we should just adopt that?

Good points

Kelvin.

Re: Layout of subproject distro downloads on people.apache.org

[Jeremy Boynes <jb...@apache.org>]

On 11/13/06, kelvin goodson <ke...@gmail.com> wrote:
>
> Whether or not we can rearrange the existing state, there is the question of
> how we proceed with holding new releases.  We have 3 (or in the C++ case 4)
> orthogonal concepts to arrange into a hierarchy (language, release,
> subproject,  with C++ also having platform).
>
> I propose that we arrange the hierarchy in the sequence -- language,
> release, subproject (platform).
>

I think that this will run into problems as we start to release
modules independently of each other. For example, we might release
multiple versions of newer modules in the lifetime of a single version
of a more mature one.

I'd suggest the switching that order to

language / module / version / variant

where variant is not just the platform variants but also the different
types of distribution such as binary, source, samples, javadoc etc.

For SDO that would be something like:
java/sdo/1.0-incubator-M2/sdo-1.0-incubator-M2.zip
java/sdo/1.0-incubator-M2/sdo-1.0-incubator-M2.tgz
java/sdo/1.0-incubator-M2/sdo-1.0-incubator-M2-source.zip
java/sdo/1.0-incubator-M2/sdo-1.0-incubator-M2-javadoc.zip
etc.

This is very similar ot the layout Maven uses for its repo - perhaps
we should just adopt that?
--
Jeremy

---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org