| Summary: | dev-libs/qcustomplot-1.3.2 stable request | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | David Flogeras <dflogeras2> |
| Component: | [OLD] Keywording and Stabilization | Assignee: | Qt Bug Alias <qt> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | Keywords: | STABLEREQ |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=572044 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 571958 | ||
|
Description
David Flogeras
2016-01-14 23:59:25 UTC
I just noticed that 1.3.2 is out - should we proceed with this request now or wait 30 days and target that instead? Matters not to me, I just wanted to get the ball rolling. Well, as long as upstream doesn't release 1.3.3 by then and we have moving target syndrome. Whatever makes the most sense to ease the burden on you guys. If you decide to wait, let me know, and I'll use the same logic on sqlitebrowser - I requested 3.7.1 which has been in tree, but 3.8.0 was just added and it will have to wait on qcustomplot for 30 days. I have no strong preference either way. I guess another pro for waiting is that if I can get ~arm keywords (just testing locally now) we could stable on arm too in 30 days? If there's no preference we may as well wait and target .2 to reduce load on the arch teams. It seems unlikely there will be further releases soon. shall we proceed? amd64 stable x86 stable arm passes, closing. |
