Hello ChangZhuo Chen. Thanks for your quick feedback.
On Fri, Oct 30, 2015 at 11:05:11PM +0800, ChangZhuo Chen wrote: > Hi, > > Thank for the information. However, I once discuss with upstream about > this and they suggest to create package when new version is released. It > would be good if someone want to cherry-pick or use git snapshot, and I > will sponsor if necessary. For me, I just want to wait for the new > release, or use git snapshot when Scretch freezes. While I normally agree that it's best to use upstream releases there are ofcourse always reasons to break the general rules. Unless you know there will very soon be a new upstream release I think this might be such an occation because: - not making the change means your package might be temporarily removed from testing (and if not fixed before freeze, miss next release). - making the change late in the release cycle (rather than now) means you might not have much time to fix any potential breakage you introduce which will likely result in your package being removed from testing during the freeze and then certainly miss the release. - the change should have happened years ago already, there's not much point in postponing it any further and blocking progress. If you make the change now, you have plenty of time to fix up any potential issues it might have before we freeze because we're still quite early in the release cycle. I'm able to upload myself and I read it as you're welcoming NMUs. I'll consider NMUing your package if needed (but I generally prefer getting packages removed when there's no maintainer who actively wants to take care of them so that will likely be my first option unless release managers thinks it's a bad idea).... Regards, Andreas Henriksson
