On 22 August 2014 13:01, Gordon Sim <[email protected]> wrote: > On 08/22/2014 12:51 PM, Rob Godfrey wrote: > >> Given the number of changes I think it might be better to simply request a >> general exception from the normal Beta release process. >> >> Unfortunately us Java guys are running a little behind schedule, and at >> the >> point the Beta was cut, the Java code was not really releasable - a lot of >> stuff not finished in the UI improvements, etc.). >> >> Since the beta was cut we've closed down pretty much all of the issues I >> think, and certainly by close of business today I believe that the trunk >> code will be in a releasable state. >> >> Given the above I'd like to request that rather than trying to merge each >> of the individual JIRAs we instead merge everything that is on trunk >> > > That's everything on trunk under 'java' right? Will also need Fraser's one > fix to the broker plugin. > > Yep, though I think the QMF plugin change may actually work even in advance of the changes to the broker that would require it to happen. If so it can be merged either way.
> > on >> Monday morning, and take that as the baseline for the first release >> candidate. If nothing else it will better reflect the code that the Java >> developers are currently testing against and fixing. >> >> What do others think? >> > > Fine by me. > > Sounds good to me too. > Generally for the future, if anyone is unhappy at the state of trunk at > the point of beta its better to raise that concern and request a > postponement in order to get things in shape before branching. Having a > planned schedule is good - it lets people know what to expect, makes it > more transparent and open - but if anyone thinks it needs to be moved a > week or two here or there they should feel free to request that. > Equally, if the release branch is created off-schedule, it would probably be a good idea to give a heads up when it is actually going to be created.
