Hi Gurkan! I think we should _not_ port back all changes we did on trunk. That would make the maintenance branch worthless. I would e.g. not port back the SPI and module changes because that means it's not a drop-in replacement anymore. I have not looked at the webbeans-cluster stuff right now. If this is not needed for most users which do not use fail-over then I can imagine that it might be ok for 1.1.7 as well. It should at least be drop in for most of our users.
Before heading to release 1.2.0 I would like to fix our Security stuff with commons-privilizer. There are for sure a few things we need to fix in both branches. E.g. making the Producers stateless and remove the CreationalContext from them. How do we handle this in JIRA? I propose to create a bug report for 1.2.0 and then create a clone for 1.1.7 just for tracking commits and to be able to get a clean release report. wdyt? Please tell us your preferences for doing a 1.2.0 release. So far we are still on CDI-1.0, releasing 1.2.0 with CDI-1.0 and later moving to 1.1 sounds a bit weird imo. LieGrue, strub ----- Original Message ----- > From: Gurkan Erdogdu <[email protected]> > To: "[email protected]" <[email protected]> > Cc: > Sent: Tuesday, November 27, 2012 11:19 AM > Subject: Re: Thoughts on OWB 1.1.7 ? > > AFAIK some fix in trunk were not ported to 1.1.7 branch. Before releasing, we > must fix these bugs. > > > > ________________________________ > Kimden: David Blevins <[email protected]> > Kime: openwebbeans-dev <[email protected]> > Gönderildiği Tarih: 27 Kasım 2012 0:52 Salı > Konu: Thoughts on OWB 1.1.7 ? > > What's the approximate timeline on 1.1.7 ? > > > -David >
