Thorsten Behrens wrote: > Stephan Bergmann wrote: >> >no, the decision was to put only final milestone builds to >> >hg.services.openoffice.org/DEV300. >> >> I think I remember there was some announcement to handle masterfixes >> differently, but cannot find it. Anyway, would it not make more >> sense to commit masterfixes directly on the master, in between >> commits of completed milestones? That way, CWS that are hit by the >> masterfixed problem could easily be updated. >> > Indeedly. Committing to DEV300_next defeats the whole purpose of > masterfixes, namely fixing the build for the people out there. Using > the next master milestone, one could simply setup a quickfix CWS, > and following the normal CWS processes. Masterfixes were > specifically designed to be _exemptions_ from the CWS process.
Just to give that discussion a good ending: master fixes we be pushed to DEV300 in the future. That was already planned to happen. But the people doing the last builds obviously haven't been aware of that, so it wasn't done. Regards, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "[email protected]". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
