On Thu, Oct 8, 2009 at 12:10 PM, Don Brown <[email protected]> wrote: > On Thu, Oct 8, 2009 at 8:10 PM, Richard S. Hall <[email protected]> wrote: >> So, once 2.2.0 is out and 2.0.x goes into mothballs as far as mainline >> development goes, then we just need to wait for the first issue to arise and >> we can set this plan into motion. Until then, please keep posting any issues >> so they can be integrated in a service release or the next release. > > Great, glad to hear we are on the same page. When will the 2.2 work > begin? As long as trunk stays with fixes for 2.0, we don't need the > branch, but as soon as the first API-changing 2.2 commit is ready, we > will.
Well, our API is the OSGi API and as we probably don't see a change there for a while we will start 2.2 when we think its necessary. Until then, trunk is going to stay with fixes for 2.0. When we start 2.2 you can certainly start backporting/fixing stuff on the old branch. regards, Karl > Don > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Karl Pauls [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
