I agree - both 270 and 283 must be included for 2.3 to be worth voting for.
Dan <[EMAIL PROTECTED]> wrote on 04/03/2008 11:25:29 AM: > 270, 283 are essentials. I'd also like to see 271 in there (I have my > own similar patch). > > -----Original Message----- > From: Kam K. Yee [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 03, 2008 5:18 PM > To: [email protected] > Subject: Re: plans for next Muse release? > > > I would like to re-post the same question... > > We, the team from IBM, have gotten the necessary internal approvals for > contributing code for the following JIRA line items: > > 242 - Security > 243 - Dynamic discovery and aggregation of resource types > 256 - Discovery based bootstrapping for advertisements > 281 - Subscription Manager must throw faults on publish back to > notification producer > 244 - Test/compliance framework for Muse > 259 - Flexible test infrastructure and initial set of extensible > functional tests > > We would like to request these to be included in the 2.3 release. > > What would be the best way to contribute the code? > > Also, JIRA items 102, 207, 252, 272, and 278 have patches attached which > we'd like to include also. > > -- > View this message in context: > http://www.nabble.com/plans-for-next-Muse-release--tp15237415p16467556.h > tml > Sent from the Muse - Dev mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > 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] >
