Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (athena.apache.org: domain of gnodet@gmail.com designates
 72.14.220.155 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=qVkJc/AT7QbQOFnxBp9x0xL/RMAq0eCismV/HQd/s+sjZL+w4Xrmw/pbHh9sPQ55A7
         lM6HiIAz2W5Ibb28+gbWMF5qIPmX9ZJAR4U2ulGrfBwtU5z84DPKbEfHv5nepuxIBwPQ
         oUDsDQrieb1qXmkv6wSSd8RKItrzlRk492IQE=
MIME-Version: 1.0
In-Reply-To: <4BC358A9.9030107@gmail.com>
References: <4BC358A9.9030107@gmail.com>
Date: Mon, 12 Apr 2010 20:46:10 +0200
Message-ID: <s2tb23ecedc1004121146y9c1c6abbp9c0b17ae7bc8a61d@mail.gmail.com>
Subject: Re: Are the specs ready to go up for a release vote?
From: Guillaume Nodet <gnodet@gmail.com>
To: dev@geronimo.apache.org, rickmcg@gmail.com
Content-Type: multipart/alternative; boundary=00151747546efbb29f04840e8e9e

--00151747546efbb29f04840e8e9e
Content-Type: text/plain; charset=ISO-8859-1

Have the specs jars been tested in both a non osgi environment and an osgi
environment ?
Also, i'd like to have the scripting api and rest api osgi-fied the same
way.  We'd need them in servicemix, and given you have rewritten the specs
to support osgi, i don't see the need to maintain the servicemix ones
anymore.
Also, I think there is an unresolved JIRA issue (GERONIMO-3960) about the
imported packages (they should not import their own packages).

On Mon, Apr 12, 2010 at 19:30, Rick McGuire <rickmcg@gmail.com> wrote:

> If we wish to release a milestone soon, we need to start getting the
> different subcomponents released fairly quickly.  Here are the things I
> believe we need to have release votes on:
>
> 1)  New spec components.  These need to be done first, and should probably
> done as a single vote rather than trying to schedule a vote for each of the
> jars.
> 2)  New javamail jar (should probably done concurrently with the javamail
> spec).
> 3)  New xmlbeans schema jar releases (java ee 1.4, java ee 5, and java ee 6
> versions)
> 4)  New components jars
> 5)  New yoko jars
> 6)  New tomcat ext jars
>
> For 1), I think these are ready to go.  I believe the issue of the package
> exports has been resolved as far as it can be for the 3.1 M1 release.  The
> jpa and servlet specs will be exporting dual version levels because the need
> to line up with different implementations that are not conforming to the
> OSGi specs yet.  This seems like a workable solution, at least for the short
> term.  I believe all of our specs are currently passing the signature tests,
> so they look clean there.  If I don't hear any objections, I'll start
> staging these for release tomorrow morning.
>
> The one spec there might be a concern about is the ccpp spec jar.  This is
> used in the pluto support currently, but we don't currently have a TCK to
> validate this one.  I need some opinions on how to proceed with that jar.
>  For now, I'll not be submitting this one for a vote with the rest of the
> specs.
>
> What state are the rest of these in?  I suspect yoko is not stable enough
> currently since David Jencks is currently working on getting the Corba
> support working.  We might want to delay the tomcat external release as long
> as we can in case we require some patches.  "As long as we can" is probably
> not more than a week.  The xmlbeans schema jars are probably pretty stable
> and capable of being released now.
>
> Are the components in any shape that release votes can be started?  Here
> are the components we need to release:
>
> - geronimo-connector
> - geronmo-transaction
> - geronimo-jaspi
>
> This will need to be handled fairly soon too.
>
> Rick
>
>


-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

--00151747546efbb29f04840e8e9e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Have the specs jars been tested in both a non osgi environment and an osgi =
environment ?<div>Also, i&#39;d like to have the scripting api and rest api=
 osgi-fied the same way. =A0We&#39;d need them in servicemix, and given you=
 have rewritten the specs to support osgi, i don&#39;t see the need to main=
tain the servicemix ones anymore.</div>
<div>Also, I think there is an unresolved JIRA issue (GERONIMO-3960) about =
the imported packages (they should not import their own packages).<br><br><=
div class=3D"gmail_quote">On Mon, Apr 12, 2010 at 19:30, Rick McGuire <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:rickmcg@gmail.com">rickmcg@gmail.com</a>=
&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">If we wish to release a milestone soon, we =
need to start getting the different subcomponents released fairly quickly. =
=A0Here are the things I believe we need to have release votes on:<br>

<br>
1) =A0New spec components. =A0These need to be done first, and should proba=
bly done as a single vote rather than trying to schedule a vote for each of=
 the jars.<br>
2) =A0New javamail jar (should probably done concurrently with the javamail=
 spec).<br>
3) =A0New xmlbeans schema jar releases (java ee 1.4, java ee 5, and java ee=
 6 versions)<br>
4) =A0New components jars<br>
5) =A0New yoko jars<br>
6) =A0New tomcat ext jars<br>
<br>
For 1), I think these are ready to go. =A0I believe the issue of the packag=
e exports has been resolved as far as it can be for the 3.1 M1 release. =A0=
The jpa and servlet specs will be exporting dual version levels because the=
 need to line up with different implementations that are not conforming to =
the OSGi specs yet. =A0This seems like a workable solution, at least for th=
e short term. =A0I believe all of our specs are currently passing the signa=
ture tests, so they look clean there. =A0If I don&#39;t hear any objections=
, I&#39;ll start staging these for release tomorrow morning.<br>

<br>
The one spec there might be a concern about is the ccpp spec jar. =A0This i=
s used in the pluto support currently, but we don&#39;t currently have a TC=
K to validate this one. =A0I need some opinions on how to proceed with that=
 jar. =A0For now, I&#39;ll not be submitting this one for a vote with the r=
est of the specs.<br>

<br>
What state are the rest of these in? =A0I suspect yoko is not stable enough=
 currently since David Jencks is currently working on getting the Corba sup=
port working. =A0We might want to delay the tomcat external release as long=
 as we can in case we require some patches. =A0&quot;As long as we can&quot=
; is probably not more than a week. =A0The xmlbeans schema jars are probabl=
y pretty stable and capable of being released now.<br>

<br>
Are the components in any shape that release votes can be started? =A0Here =
are the components we need to release:<br>
<br>
- geronimo-connector<br>
- geronmo-transaction<br>
- geronimo-jaspi<br>
<br>
This will need to be handled fairly soon too.<br><font color=3D"#888888">
<br>
Rick<br>
<br>
</font></blockquote></div><br><br clear=3D"all"><br>-- <br>Cheers,<br>Guill=
aume Nodet<br>------------------------<br>Blog: <a href=3D"http://gnodet.bl=
ogspot.com/">http://gnodet.blogspot.com/</a><br>------------------------<br=
>
Open Source SOA<br><a href=3D"http://fusesource.com">http://fusesource.com<=
/a><br><br><br>
</div>

--00151747546efbb29f04840e8e9e--