2013/1/6 Hans Joachim Desserud <[email protected]>: > > Thank you for uploading a newer version.
You're welcome. We're glad of having a new version as well :-) > Btw, I was aware Debian was frozen, preparing for the release of Wheezy. > However, I had seen other packages upload newer versions to unstable after > the freeze started. It's a complicate process and difficult to explain briefly, I'll try. Basically, release managers very much favour updates to testing when done through unstable. If somebody reports a serious problem to "flare 0.15.1-1", in testing and unstable, we upload a new small fix to unstable and request release managers to unblock the migration to testing (blocked automatically because of the freeze), and usually there's no problem. This can be also done by uploading packages to "testing-proposed-updates", but it's a process more involved, gives more work to the release managers, if everybody does this the release gets delayed more and more, people get more grumpy, etc -- so it's better to avoid it in general. Some packages are important enough that they have special privileges (think Firefox, DB servers), especially when they are "leaf" or "near-leaf" packages (not libraries, like libc or SDL), and thus its upgrade doesn't usually affect other packages. Also, maintaners often do that *after special pre-approval from release managers*, which after a few days approve the unblock to testing (which, overall, is more work for everybody). I asked for a special request for Flare shortly after the freeze, but since 0.16 was not released yet it was not granted [1]. 0.16 was too short lived anyway, a burst of updates happened just after that (so it was clear that if 0.16 had problems, upstream would not fix them with a 0.16.1 release). So after all, it was too late for flare post-0.15 to become part of the next stable. [1] http://lists.debian.org/debian-release/2012/07/msg00443.html Sometimes, maintainers also upload their packages to unstable directly, perhaps inadvertently, and then it's more problematic for everybody in the case that some problem arises. If we did that with flare, due to its low importance and [as yet] low popularity, maybe 0.15 would be removed altogether if a serious problem is reported (say, failure to run in most architectures, frequent crashes, etc). Cheers. -- Manuel A. Fernandez Montecelo <[email protected]> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
