3.0 Milestone Release?

[Kevan Miller <ke...@gmail.com>]

I'm curious to hear the community's thoughts about starting to pull together a 3.0 Milestone release. I think there's been a lot of progress on trunk and that it would be valuable to start pulling things together for a release. 

If anything, just planning for a release starts to identify hat parts are missing and what needs to be done. Also, gives users a chance to start focusing on what features they are going to need...

Thoughts?

--kevan

Re: 3.0 Milestone Release?

[Kevan Miller <ke...@gmail.com>]

On Mar 31, 2010, at 10:40 AM, Rick McGuire wrote:

> 2)  For our dependencies, will we need real releases, or will we ship snapshots based on know revision levels?

Definitely real releases, IMO. 

If we have specific instances where we don't think this is possible, we can discuss alternatives. The only alternative release technique that I'd consider is to release out of geronimo/external/, but would really, really rather not...

--kevan

Re: 3.0 Milestone Release?

[Rick McGuire <ri...@gmail.com>]

On 3/31/2010 9:58 AM, Donald Woods wrote:
> +1 to a milestone release.  Would be great to see at least one every
> quarter until 3.0 is released.
>
> Would M1 be focused on Aries + available Java EE 6 and OSGi components,
> like RFC66, JPA 2.0, Servlet 3.0 preview, ....
>    

That sounds like a good focus, though I'm not too sure about whether 
we'll have a full Servlet 3.0 version available in the very near 
future.  The Aries support is looking like it's in pretty good shape 
with Jarek's recent success in deploying the Aries sample applications 
on Geronimo 3.0.  We're also in pretty good shape with the OSGi components.

As far as the Java EE 6 features, we have all of the APIs in place now, 
but we don't really have a lot of the providers available for these new 
features.  Servlet 3.0, the new OpenEJB features, and JSR 299/330 
support are probably the biggest laggers right now.

Given the state of the Aries integration work, we probably should start 
start work on moving toward a M1 release now.  I do have a few questions 
about what needs to be done from here:

1)  What additional features do we feel we need to complete before 
releasing the milestone.
       a)  Are there any additional features in the Aries integration 
that should be completed for the M1?
       b)  What Java EE features should we have working for this release?

2)  For our dependencies, will we need real releases, or will we ship 
snapshots based on know revision levels?

Rick
>
> -Donald
>
>
> On 3/29/10 3:42 PM, Kevan Miller wrote:
>    
>> I'm curious to hear the community's thoughts about starting to pull together a 3.0 Milestone release. I think there's been a lot of progress on trunk and that it would be valuable to start pulling things together for a release.
>>
>> If anything, just planning for a release starts to identify hat parts are missing and what needs to be done. Also, gives users a chance to start focusing on what features they are going to need...
>>
>> Thoughts?
>>
>> --kevan
>>      
>    

Re: 3.0 Milestone Release?

[Donald Woods <dw...@apache.org>]

+1 to a milestone release.  Would be great to see at least one every
quarter until 3.0 is released.

Would M1 be focused on Aries + available Java EE 6 and OSGi components,
like RFC66, JPA 2.0, Servlet 3.0 preview, ....


-Donald


On 3/29/10 3:42 PM, Kevan Miller wrote:
> I'm curious to hear the community's thoughts about starting to pull together a 3.0 Milestone release. I think there's been a lot of progress on trunk and that it would be valuable to start pulling things together for a release. 
> 
> If anything, just planning for a release starts to identify hat parts are missing and what needs to be done. Also, gives users a chance to start focusing on what features they are going to need...
> 
> Thoughts?
> 
> --kevan

Re: 3.0 Milestone Release?

[Ivan <xh...@gmail.com>]

A milestone release might be a good report for what we have done. I wish to
include some servlet 3.0 updates that I am working now.

2010/3/30 Kevan Miller <ke...@gmail.com>

> I'm curious to hear the community's thoughts about starting to pull
> together a 3.0 Milestone release. I think there's been a lot of progress on
> trunk and that it would be valuable to start pulling things together for a
> release.
>
> If anything, just planning for a release starts to identify hat parts are
> missing and what needs to be done. Also, gives users a chance to start
> focusing on what features they are going to need...
>
> Thoughts?
>
> --kevan




-- 
Ivan

Re: 3.0 Milestone Release?

[chi runhua <ch...@gmail.com>]

And we could deliver some documents for 3.0 Milestone such as:
   1. how to build and run the 3.0 M1;
   2. how to deploy Aries Blog sample(Jarek already wrote the instructions)
on 3.0 M1;
   3. how OGSi was integrated with Geronimo;
   4. (if more, please append the list)

Meanwhile, we could start creating the WIKI space for Geronimo 3.0.

Any comments?

Jeff


On Wed, Apr 7, 2010 at 8:59 AM, Ivan <xh...@gmail.com> wrote:

> Usually we have two distributions, Tomcat and Jetty, so do we publish both
> ?
> I think we might just focus one container at this time, thought ?
>
> 2010/4/5 Jarek Gawor <jg...@gmail.com>
>
> A few thoughts:
>>
>> 1) Yes, I think it would be good to have a milestone release to show
>> some of the Aries + Java EE 6 stuff.
>>
>> 2) I am concerned about the number of snapshot dependencies and the
>> time would take to release them all for the milestone.  So we should
>> start releasing stuff now... but at the same time we should consider
>> what happens if we can't get everything released in time. That is,
>> should we consider removing certain components from the release or
>> releasing the milestone with some snapshot dependencies. In general, I
>> have no problem with either options. This is a milestone release so it
>> doesn't have to be perfect.
>>
>> 3) Things that I think we should get done before/for the milestone: a)
>> make sure the testsuites are running, b) figure out how to deal with
>> the endorsed libraries in maven.
>>
>> Jarek
>>
>> On Mon, Mar 29, 2010 at 3:42 PM, Kevan Miller <ke...@gmail.com>
>> wrote:
>> > I'm curious to hear the community's thoughts about starting to pull
>> together a 3.0 Milestone release. I think there's been a lot of progress on
>> trunk and that it would be valuable to start pulling things together for a
>> release.
>> >
>> > If anything, just planning for a release starts to identify hat parts
>> are missing and what needs to be done. Also, gives users a chance to start
>> focusing on what features they are going to need...
>> >
>> > Thoughts?
>> >
>> > --kevan
>>
>
>
>
> --
> Ivan
>

Re: 3.0 Milestone Release?

[Ivan <xh...@gmail.com>]

Usually we have two distributions, Tomcat and Jetty, so do we publish both ?

I think we might just focus one container at this time, thought ?

2010/4/5 Jarek Gawor <jg...@gmail.com>

> A few thoughts:
>
> 1) Yes, I think it would be good to have a milestone release to show
> some of the Aries + Java EE 6 stuff.
>
> 2) I am concerned about the number of snapshot dependencies and the
> time would take to release them all for the milestone.  So we should
> start releasing stuff now... but at the same time we should consider
> what happens if we can't get everything released in time. That is,
> should we consider removing certain components from the release or
> releasing the milestone with some snapshot dependencies. In general, I
> have no problem with either options. This is a milestone release so it
> doesn't have to be perfect.
>
> 3) Things that I think we should get done before/for the milestone: a)
> make sure the testsuites are running, b) figure out how to deal with
> the endorsed libraries in maven.
>
> Jarek
>
> On Mon, Mar 29, 2010 at 3:42 PM, Kevan Miller <ke...@gmail.com>
> wrote:
> > I'm curious to hear the community's thoughts about starting to pull
> together a 3.0 Milestone release. I think there's been a lot of progress on
> trunk and that it would be valuable to start pulling things together for a
> release.
> >
> > If anything, just planning for a release starts to identify hat parts are
> missing and what needs to be done. Also, gives users a chance to start
> focusing on what features they are going to need...
> >
> > Thoughts?
> >
> > --kevan
>



-- 
Ivan

Re: 3.0 Milestone Release?

[Jarek Gawor <jg...@gmail.com>]

A few thoughts:

1) Yes, I think it would be good to have a milestone release to show
some of the Aries + Java EE 6 stuff.

2) I am concerned about the number of snapshot dependencies and the
time would take to release them all for the milestone.  So we should
start releasing stuff now... but at the same time we should consider
what happens if we can't get everything released in time. That is,
should we consider removing certain components from the release or
releasing the milestone with some snapshot dependencies. In general, I
have no problem with either options. This is a milestone release so it
doesn't have to be perfect.

3) Things that I think we should get done before/for the milestone: a)
make sure the testsuites are running, b) figure out how to deal with
the endorsed libraries in maven.

Jarek

On Mon, Mar 29, 2010 at 3:42 PM, Kevan Miller <ke...@gmail.com> wrote:
> I'm curious to hear the community's thoughts about starting to pull together a 3.0 Milestone release. I think there's been a lot of progress on trunk and that it would be valuable to start pulling things together for a release.
>
> If anything, just planning for a release starts to identify hat parts are missing and what needs to be done. Also, gives users a chance to start focusing on what features they are going to need...
>
> Thoughts?
>
> --kevan