Hi Zoltán, > I know correctly that the latest integrated into m106 database connected > cws was dba34d. > The fs34b in finished status, and fs34 fixed two issue and still open, > the hsqldb19 approved by QA still wait for DEV300 integration. > > In EIS i found that is nmerged to cws > dba34d:
No, it is the other way 'round: dba34d was merged into fs34b. Sorry, my wording in EIS could have been better :) > But I fuond in OOO340m0/DEV300m106 that for example, bug 117454 old > report, and bug 117472 is still in. > That means fs34b not merged correctly. Not sure at the moment what the "finished" status for fs34b is supposed to tell us - at least it implies "not integrated, yet". <http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=10194&logon=true&OpenOnly=false&TasksInline=false&Section=Overview> says that fs34b is in status "integrated", but the "Milestone (integrated)" field is empty - this means that the milestone which the CWS has been integrated into has not been finished, but is ongoing - which means the CWS will be in OOO340.m1. If it were in OOO320.m0, then the "Milestone (integrated)" field would be filled, since m0 is done already. So, the bottom line is: No surprise that fs34b's bugs are not fixed in m0, expect the fixes for m1. As far as I know, m1 has been built already, or at least it was started (since I got questions 'bout some build breakers caused by a flawed integration of another CWS of mine :) ). Not sure whether it is finished. Also, I don't know the timeline for the upcoming builds, but I know that I am not the only one who thinks we (whatever "we" means in this context) should at least release a proper 3.4. But again, there's still some dust in the air, which might need to settle beforehand ... Ciao Frank -- ----------------------------------------------------------------- To unsubscribe send email to dev-unsubscr...@dba.openoffice.org For additional commands send email to sy...@dba.openoffice.org with Subject: help
