Bug#996726: Some other questions

[Bob Wong]

  For example, now the gcc version in the bookworm is 11.2.0-2, now the
maintainer of the package upload a new version. I suppose it is 11.2.0-3.
Normally, it will be pushed into the bookworm after 5 days. Now we assume a
package relied on the package updated after one day. Normally it will be
pushed into the bookworm one day later than the gcc update. Here I mean
push the gcc and that package together to the bookworm. This is for single
package. For the whole Debian project, that is to say do a small release
every 10 days and not roll package one by one.

Norbert Preining  于2021年11月6日周六 下午8:44写道：

>
>
> > to make each package synced downstream at the same time, but it's too
> hard
> > to achieve.
>
> ??? Not sure what you want to say here ...
>

Bug#996726: Some other questions

[Bob Wong]

  Probably the best way is to do the rolling release. Another solution is
to make each package synced downstream at the same time, but it's too hard
to achieve.

Jérôme Pouiller  于2021年11月5日周五 下午6:11写道：

> On Friday 5 November 2021 03:02:13 CET Norbert Preining wrote:
> > >   After 2 weeks, the bug has finally been fixed. But I wonder why the
> bug
> > > wasn't tested out in the unstable branch and was pushed into the
> testing
> >
> > Because on unstable everything worked. The bug happens only due to
> > different transition times from unstable to testing. This cannot be
> > tested in unstable before.
>
> Is there a way to avoid this problem happen in the future?
>
> --
> Jérôme Pouiller
>
>
>

Bug#996726: Some other questions

[Bob Wong]

  After 2 weeks, the bug has finally been fixed. But I wonder why the bug
wasn't tested out in the unstable branch and was pushed into the testing
branch.