| 1 |
On Sat, 2019-11-16 at 14:55 +0100, Ulrich Mueller wrote: |
| 2 |
> > > > > > On Fri, 15 Nov 2019, Michael Orlitzky wrote: |
| 3 |
> > Two things on that page are outright wrong: |
| 4 |
> > 1. If the package has stable keywords, they should be moved to the |
| 5 |
> > new revision without dropping. To commit the ebuild, repoman |
| 6 |
> > commit --straight-to-stable option should be used. |
| 7 |
> > That violates our other stabilization policies and common sense. |
| 8 |
> |
| 9 |
> This is in the context of revision bumps, not version bumps. Also, the |
| 10 |
> item immediately preceding it clarifies that any non-trivial changes |
| 11 |
> require dropping to ~arch. |
| 12 |
> |
| 13 |
|
| 14 |
More precisely, this is in context of dependency corrections. There is |
| 15 |
no need to go through stabilization to restrict too broad dependency |
| 16 |
specifications, while stable users hit the issue for the next two |
| 17 |
months. |
| 18 |
|
| 19 |
-- |
| 20 |
Best regards, |
| 21 |
Michał Górny |
Archives