Hi Sascha,
On Sat, Dec 13, 2014 at 11:36:19AM +0000, Sascha Steinbiss wrote:
> I have a question regarding the jessie freeze policy. In the policy
> document (https://release.debian.org/jessie/freeze_policy.html) it says
> that one should "keep disruptive changes out of unstable and continue
> making use of experimental for changes that are not suitable for jessie."
>
> I have just uploaded a new version of a package (new GenomeTools
> upstream version) to experimental, fixing many original upstream bugs
> and introducing new features. It is a dependency for another package and
> contains a library. As this new release contains a fix for a bug which
> has been quite common for a while and a major source of tickets in the
> upstream issue tracker, I would really like to make sure that
>
> a) current unstable users get the new version, and
>
> b) Ubuntu picks up the new version until their Debian import
> freeze in Feb 2015 (they import from unstable),
>
> do you see much in the way of uploading this package to unstable as well?
You always need to outweight policy with sane reasons / common sense.
If you think GenomeTools and its dependencies will pretty surely not
feature any RC bug we will probably not need to keep new versions out of
unstable. But how can you surely know this? I think by waiting a
certain time to see whether some QA tools have run once or twice which
is probably in a one month time frame. So if you are sure the Debian
import Freeze for Ubuntu will be Feb 2015 it might be the best compromise
to upload GenomeTools (and its dependencies) in mid January which should
be sufficient to a) reach Ubuntu and b) uncover any RC bugs in testing.
Kind regards
Andreas.
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141213135012.ga2...@an3as.eu
