| Summary: | =media-gfx/rawtherapee-5.2 stabilization request | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Francesco Riosa <vivo75> |
| Component: | Stabilization | Assignee: | Francesco Riosa <vivo75> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | franz.trischberger, graphics+disabled, jstein, mgorny, proxy-maint, vivo75 |
| Priority: | Normal | Keywords: | STABLEREQ |
| Version: | unspecified | Flags: | stable-bot:
sanity-check+
|
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=632592 | ||
| Whiteboard: | |||
| Package list: |
=media-gfx/rawtherapee-5.2
|
Runtime testing required: | --- |
|
Description
Francesco Riosa
2017-05-13 00:06:27 UTC
May I suggest to go with 5.1 now? It's in the tree long enough. Also 5.0 suffers from bad crashes that are fixed in 5.1: https://github.com/Beep6581/RawTherapee/issues/3787 We could add the patch to 5.0, of course. The 5.1 release also got some great performance improvements, so in the end I think it would be better to make 5.1 stable. We also got a 5.2 release some hours ago, so I hope we get this STABLERQ fixed before 5.2 is in the tree for 2 months :) (In reply to Franz Fellner from comment #1) > May I suggest to go with 5.1 now? It's in the tree long enough. > Also 5.0 suffers from bad crashes that are fixed in 5.1: > https://github.com/Beep6581/RawTherapee/issues/3787 > We could add the patch to 5.0, of course. > > The 5.1 release also got some great performance improvements, so in the end > I think it would be better to make 5.1 stable. > > We also got a 5.2 release some hours ago, so I hope we get this STABLERQ > fixed before 5.2 is in the tree for 2 months :) PING 2 months passed and 5.3 is out. > 2 months passed and 5.3 is out.
I'll provide an updated ebuild for RT 5.3 to the proxy maintainers the coming days.
For stabilization I'll check the requirements:
☑ The package has spent a reasonable amount of time in ~arch first. Thirty days is the usual figure, although this is clearly only a guideline. For critical packages, a much longer duration is expected. For small packages which have only minor changes between versions, a shorter period is sometimes appropriate.
☐ The package must not have any non-arch dependencies.
☑ The package must not have any severe outstanding bugs or issues.
☑ The package must be widely tested.
☑ If the package is a library, it should be known not to break any package which depends upon it.
And request the amd64 team to stabilize
☑ The package must not have any non-arch dependencies. checked this one too Feel free to CC arches. (In reply to Michał Górny from comment #5) > Feel free to CC arches. Done yesterday, only amd64 and x86 are involved since the package is keyworded only ~amd64 and ~x86. Can we have a fix for the QA warnings first? see. 632592 That would increase the quality a lot before stabilizing it. https://github.com/gentoo/gentoo/pull/5837 has the QA warning fix obviously it's https://github.com/gentoo/gentoo/pull/5853 5837 has already been accepted x86 stable ping Stable on amd64. |
