Re: [Python-modules-team] Bug#699312: Bug#699312: pytest version in raring is old
On 16 February 2013 18:10, Simon Chopin <email@example.com> wrote:
> Hello Joseph,
> Quoting Joseph Tate (2013-01-30 05:27:08)
>> I've updated the version of pytest to the latest upstream. It doesn't need to be backported, I would just like to see the version in raring be updated.
>> *** /tmp/tmpKV7SC6/bug_body
>> In Ubuntu, the attached patch was applied to achieve the following:
>> * New upstream release, backport to precise
>> Thanks for considering the patch.
> As you might not be aware of, Debian testing is currently frozen, which
> means that to keep a clear migration path for RC bug fixes I avoid
> uploading new upstream versions to unstable at this time.
> However, I'm considering uploading this new upstream version to
> experimental as soon as I've figured out how the DPMT deals with
Some started pushing experimental to trunk, expecting no further
uploads into sid.
Some create branches/experimental if they expect to keep the two in parallel.
Just do it, and tag it, one can always branch from a tag if further
uploads to sid are required.
Although a consensus would be nice.
d-i team for example is using a "jessie" branch name for things that
should atm be uploaded into experimental.