Hi Thomas and Julien The 2012.1-6 upload was done before the freeze and the plan was to have it included in testing before the freeze. Apparently that did not happen. I was under the impression that the freeze would be to uploads after the freeze, not to the packages that had not yet done the transition. Apparently I was wrong, and if that have cause this problem, I'm sorry for that.
We did not have any bug report about the issues for that change. Instead I did those changes in order to solve problems that were similar to issues in other packages. It was more of a cleanup work in order to avoid bug reports in the future. We did have issues with the conflicts, replaces, breaks in other packages and if I remember correctly they were important also for this package. It is some time since I did this so I do not remember all the details. I think the 2012.1-6 upload was a good thing for the package, especially for upgrade from earlier versions. That is however not such a big problem for this release as it has not been part of stable before. It may be an issue for later releases though. >From a release team perspective I understand that you do not want large last minute changes to packages. I can not motivate the change to be that strong to be forced in. If you want I can make a proposed patch based on the changes Thomas made for 2012.1-7 and void the changes for 2012.1-6. I do however think the changes done in 2012.1-6 was good and we should have them in for next release (after the one that is frozen now). This means that I do not think we should revert them for next release, but I do not have a big problem to do it for testing. I hope this clarifies the situation a bit. Cheers, // Ola tis 2012-11-13 klockan 20:16 +0800 skrev Thomas Goirand: > On 11/13/2012 07:08 PM, Julien Cristau wrote: > > On Fri, Nov 9, 2012 at 05:03:58 +0800, Thomas Goirand wrote: > > > >> Please let me know if the attached patch would be accepted by the > >> release team and avoid Quantum to be removed. > >> > > Sigh. If you want to be sure it'll be accepted then just upload the > > minimal fix for the RC bug and leave it at that (2012.1-6 doesn't seem > > to list a bug number, so without more explanations it doesn't qualify). > > As I wrote, these changes were not mine. I don't think it's appropriate > to write "sigh" or to be pissed *at me*. The only thing I did was > working on the issue the release team cared about, and fixing it, I'm > not responsible for the other changes, and I don't intend to assume > responsibility for them regarding the unblock. > > It wasn't nice that these changes were uploaded without caring about the > SID to Wheezy migration. Numerous times, I wrote about it to both Ola > and Loic. I'm not surprised about the resulting conversation with the > release team. But since that's not my work, and that I would like to > respect what the others do, I still want to leave them the job to answer > about it. > > So please, Ola and Loic, explain and deal with the release team. If you > guys think the changes are necessary, tell why. If you think they should > be removed, please do the necessary "git revert" (or at the very least, > let me know that you would agree if I was to do it). > > And finally, I hope this is a lesson and that it wont happen again, and > that you will bare with me and the rest of the PKG Openstack team. > > > I'm not going to review every single one of your uploads 5 times. > > You don't have to, you can accept it the first time! :) > > Thomas > -- --- Inguza Technology AB --- MSc in Information Technology ---- / o...@inguza.com Annebergsslingan 37 \ | o...@debian.org 654 65 KARLSTAD | | http://inguza.com/ Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --------------------------------------------------------------- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org