Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 579816 - =net-firewall/shorewall-5.0.7.2: Fast track stabilisation request
Summary: =net-firewall/shorewall-5.0.7.2: Fast track stabilisation request
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Thomas Deutschmann (RETIRED)
URL:
Whiteboard:
Keywords: ALLARCHES, STABLEREQ
Depends on:
Blocks:
 
Reported: 2016-04-13 08:45 UTC by Tony Vroon (RETIRED)
Modified: 2016-08-13 00:29 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tony Vroon (RETIRED) gentoo-dev 2016-04-13 08:45:20 UTC
Shorewall 5.0.6 and later offer Docker co-habitation support. With intermediate versions removed and 5.0.4 the last stable, this is not yet available in the tree. Arches, please test & mark stable:
=net-firewall/shorewall-5.0.7.2

This package was added to the tree 12 days ago. No bugs resulted.
Comment 1 Thomas Deutschmann (RETIRED) gentoo-dev 2016-04-13 11:43:53 UTC
I have deliberately chosen to skip versions between 5.0.4 and 5.0.7.2 for stabilization. These versions contain serious bugs (for example see bug 578076).

shorewall-5.0.7.2 is my current candidate for stabilization. However I don't understand why we cannot wait 30 days. Like you said, after v5.0.4 new features like explicit Docker support were introduced. But isn't that the purpose of Gentoo's stabilization policy to wait and test new versions before stabilization?

If there's a reason why you cannot wait two more weeks please share and explain why an exception of Gentoo's general stabilization policy is justified.
Comment 2 Tony Vroon (RETIRED) gentoo-dev 2016-04-13 12:19:08 UTC
Because the skipping/removal of versions, the current stable is actually 2 months old already. It breaks on Docker systems in quite unhelpful ways, for which fixes have been introduced.
The 5.6 breakages were spotted in under a week, and we are approaching two weeks here. A reasonable timeframe for a "fast track" stabilisation.

Note that the 30 days is simply a guideline and not a law. It is a balance between software freshness and stability; from the looks of things we are swinging too far towards stability here at the cost of freshness/usability.
Comment 3 Thomas Deutschmann (RETIRED) gentoo-dev 2016-04-13 12:47:51 UTC
Well, the current stable version doesn't *break* something. It is lacking of explicit Dockers support but a missing feature cannot break something.

But OK. I would have had already started stabilization of shorewall v5.0.6 if we wouldn't have experienced bug 578076.

So please proceed with stabilization.

ALLARCHES policy does apply.
Comment 4 Agostino Sarubbo gentoo-dev 2016-05-13 08:45:03 UTC
amd64 stable
Comment 5 Tobias Klausmann (RETIRED) gentoo-dev 2016-05-31 13:57:57 UTC
Stable on alpha.
Comment 6 Agostino Sarubbo gentoo-dev 2016-06-25 20:52:18 UTC
x86 stable
Comment 7 Agostino Sarubbo gentoo-dev 2016-07-06 09:46:49 UTC
ppc stable
Comment 8 Jeroen Roovers (RETIRED) gentoo-dev 2016-08-04 08:58:15 UTC
Stable for HPPA PPC64.
Comment 9 Thomas Deutschmann (RETIRED) gentoo-dev 2016-08-13 00:29:20 UTC
Closing, remaining architecture (sparc) was stabilized using the ALLARCHES policy:

> commit 35d9a27dbe3ab933502d2d1884630e50e9187389
> Author: Thomas Deutschmann
> Date:   Sat Aug 13 02:19:00 2016 +0200
> 
>     net-firewall/shorewall: Retroactively mark stable for the remaining arches using the ALLARCHES policy
> 
>     Gentoo-Bug: https://bugs.gentoo.org/579816
> 
>     Package-Manager: portage-2.3.0