Breezy Release Update (upstream version freeze TOMORROW)

[Reinhard Tartler]

On 7/6/05, Colin Watson <cjwatson at ubuntu.com> wrote:
> The deadline for pending merges from Debian to be complete was
> previously 14th July, but since that falls during Debconf this will be
> extended by one week.

Please correct me if I'm wrong, but I assume this is the date when
auto syncing from debian stops, right?

How should we MOTU's proceed after that date when a package gets
updated (no new upstream or a really small maintenance upstream
release) in debian fixing some important bug?

Let's assume we have a package foo_1.2-3 in ubuntu and the debian
maintainer uploads version foo_1.2-4 fixing an important bug.

I see some choices:

1. Add the package on https://wiki.ubuntu.com/MOTUToSync and hope the
ftpmaster will sync it

2a Upload it as Version 1.2-4 with adjusted upload target in the
makefile (and really no changes)

2b Upload it as Version 1.2-4ubuntu1 (documenting 

3. backport the changes and make upload a fixed 1.2-3ubuntu1 package?

Would Option 2a keep the package being autosync'ed again after breezy's release?


And next question, what about NEW Packages? As you can see on
http://siretart.tauware.de/revu the queue for NEW Packages is quite
long, and I don't expect it to get  shorter in the near future. May we
upload NEW Packages regardless the Upstream Version freeze in
univserse/multiverse?


What about packages from 3rd party repositories, like those from
apt-get.org or marillats repository? Are they affected by upstream
version freeze, too?

-- 
regards,
    Reinhard