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? Best regards -- Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
