Hi Justin, on the Java Broker we're doing a fair amount of work on a new web-based management console which we want to have in for 0.18. We're currently doing this work on a branch that's tracking trunk. We *could* merge this to trunk now, but we prefer only to merge work which is fully completed and tested (the branch is pretty much alpha quality right now).
Given that pretty much all the Java Broker developers are working on this, and the change is essentially orthogonal to the rest of the Java Broker... do you have any objections if we delay merging this down until closer to the July 2nd date? I think this actually decreases risk for the 0.18 release as by the time we merge down we'll be more confident that there's no showstoppers being put onto the trunk ahead of the 0.18 branch. Cheers, Rob On 12 June 2012 04:49, <[email protected]> wrote: > Hi, folks. The time for 0.18 alpha is rapidly approaching, and beta soon > after. I've adjusted the dates to allow a little more time for development, > since this warning comes rather late. > > 0.18 alpha, 18 June Deadline for major features and disruptive > changes > > 0.18 beta, 2 July We branch for release, and 0.19 opens > > Contact me if there's something you'd like to get in for 0.18, and we can > figure out where it fits. > > Thanks, > Justin > > --------------------------------------------------------------------- > 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]
