There are three primary things: SDO, DAS and SCA. For each of those
there are different artifacts we are releasing:
* the source distro (zip and tgz)
* the binary distro (zip and tgz)
* the maven artifacts that will loaded into the m2-incubator-
repository (jar and pom for each)
The first two of those are packaged distros (a big jar/tgz the user
downloads/installs).
The maven artifacts are posted to the repo so that people using maven
can download them. Some things like the poms and plugins are only
distributed this way.
These three have a dependency on two maven artifacts (the parent pom
and the buildtools) in order to build; i.e. in order to build a sdo,
das or sca source distro they need to be able to locate the parent
pom and buildtools. For this to work we need to have a released
version of these available when we tag sdo, das, sca so they can
build. I went into the details of this in a previous reply.
In M1 we did not have the separate distros and bundled everything
together. We decided with M2 to make this modular which is why we
need to release the dependencies first (which is this vote). This is
identical to how other projects coordinate releases (e.g. Axis2
needing to get releases of the WS commons projects first).
We can still release the three primary things at the same time (which
would mean one vote on all three) or we can release them separately
(one vote on each for three in all), or in some combination thereof.
--
Jeremy
On Oct 6, 2006, at 4:44 AM, ant elder wrote:
I'd really like to understand what is being proposed for all the
different
things being released and what votes we're going to be asking for
from the
Incubator PMC before I'd be willing to +1 this.
What is the M2 release - one thing and a single IPMC vote or lots
of things
and lots of votes? I guess from this and what you said on IRC M2 is
several
things which makes me worry about getting all the IPMC votes
through in a
reasonable time, especially with the C++ release also being imminent.
Could you list out what you see as the things being released and
the votes
we're going to be asking for?
...ant
On 10/6/06, Jeremy Boynes <[EMAIL PROTECTED]> wrote:
Any other votes on this?
--
Jeremy
On Oct 2, 2006, at 8:28 AM, Jeremy Boynes wrote:
> The parent pom and buildtools are pre-reqs for all other Java
> projects in the M2 release. These are distributed through the maven
> repo rather than as a end-user distribution. Please vote to approve
> the release content:
>
> parent-pom
> [tag] https://svn.apache.org/repos/asf/incubator/tuscany/tags/
> java-pom-parent/1
> [binary] http://people.apache.org/repo/m2-incubating-repository/
org/
> apache/tuscany/parent/1-incubator/
>
> buildtools
> [tag] https://svn.apache.org/repos/asf/incubator/tuscany/tags/
> java-buildtools/1.0-incubator-M2
> [binary] http://people.apache.org/repo/m2-incubating-repository/
org/
> apache/tuscany/buildtools/1.0-incubator-M2/
>
> Here's my +1
> --
> Jeremy
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
