2011/7/14 Dagobert Michelsen <[email protected]>: > Hi Maciej, > > Am 14.07.2011 um 09:53 schrieb Maciej Bliziński: >> 2011/7/14 Ben Walton <[email protected]>: >>> This works for me. There is still some work to do to automate the >>> flow and we can't sit on packages until everything is ready. Would >>> anyone like the job of moving packages from unstable to current for >>> the time being? >> >> Moving packages from unstable to current in the database can be >> automatic. How about the following idea: >> >> - maintainers push packages to unstable >> - at time t, a script looks at the diff between unstable and current; >> it prepares a change set to be applied to current; it sends the change >> set to a mailing list with information: "At time t + 12h the following >> changes will be applied: ..." >> - people in the project have 12h to react if the change set reads >> "destroy the world" >> - if no action is taken until t + 12h, the change set is applied and >> new current is pushed > > Ok. And later on packages with open bugs will be blocked from propagation, > right?
Yes, but there are some issues. This hasn't been implemented yet, and there's a bit of yak shaving to be done: - write the integration using mantis XML RPC - mantis XML RPC requires upgrading mantis - upgrading mantis requires porting our patches - porting our patches requires profiling of mantis So for now, I thought of unconditional migration with monitoring and optional human intervention. Maciej _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
