Few days in the tree, but just contains fixes for some qa issues and EAPI=5. target KEYWORDS="amd64 ppc sparc x86"
Also please drop old revision.
No, it is too soon. No reason to break the 30-day rule unless it is absolutely necessary (or fixes security problems)
(In reply to comment #2) > No, it is too soon. No reason to break the 30-day rule unless it is > absolutely necessary (or fixes security problems) the diff shows just an eapi bump, the logic seems to be similar.
(In reply to comment #3) > (In reply to comment #2) > > No, it is too soon. No reason to break the 30-day rule unless it is > > absolutely necessary (or fixes security problems) > > the diff shows just an eapi bump, the logic seems to be similar. Why is it so urgent to stabilize it?
As i was informed, the 30-day rule is not a rule, so lets do it (excluding ppc as it was not stable for them before)
amd64 stable (In reply to comment #5) > As i was informed, the 30-day rule is not a rule, so lets do it I saw many times that revbump(NOT version bump) usually can omit 30 days rule for stabilization
x86 stable
sparc stable. Last arch, closing