Re: soft freeze

2017-01-14 Thread Jonas Smedegaard
Quoting Ralf Treinen (2017-01-14 15:31:19) > Hi, I was under the impression that during the soft freeze (i.e, now) > new usptream versions of packages that are already in testing are > blocked from migrating. However, I can't find anything to this effect > in the announcemen

Re: soft freeze

2017-01-14 Thread Sebastiaan Couwenberg
On 01/14/2017 03:47 PM, Pirate Praveen wrote: > Sebastiaan Couwenberg wrote: >> No new source packages are allowed into stretch, new upstream >> versions of packages which are in testing are still allowed. > > Is this applicable to new dependencies required for updating an > existing package as w

Re: soft freeze

2017-01-14 Thread Pirate Praveen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Sebastiaan Couwenberg wrote: > No new source packages are allowed into stretch, new upstream > versions of packages which are in testing are still allowed. Is this applicable to new dependencies required for updating an existing package as well? Fo

Re: soft freeze

2017-01-14 Thread Sebastiaan Couwenberg
On 01/14/2017 03:31 PM, Ralf Treinen wrote: > Hi, I was under the impression that during the soft freeze (i.e, now) new > usptream versions of packages that are already in testing are blocked > from migrating. However, I can't find anything to this effect in the > announcemen

soft freeze

2017-01-14 Thread Ralf Treinen
Hi, I was under the impression that during the soft freeze (i.e, now) new usptream versions of packages that are already in testing are blocked from migrating. However, I can't find anything to this effect in the announcements by the release team. Can please someone in the know confir