as unifi have Stable Candidate and Stable release cycle, https://community.ubnt.com/t5/UniFi-Wireless/Notes-on-UniFi-releases-Stable-Candidate-Stable-repos-download/m-p/1800676#M203780 I think at least keep few stable version back in case anything go wrong is a better approach, and they screwed up A LOT. as current view on portage unifi-5.6.40.ebuild [current LTS, probably good for remove ~amd64 unifi-5.10.15.ebuild [screwed up stable candidate be replaced by next version in one day unifi-5.10.16.ebuild [current stable candidate the old stable version just gone, which is kind inconvenient.
My current policy has been to always keep 2 versions for each supported series. I'm not strictly following when they are beta versus stable candidate versus stable. Is 5.10.16 not working for you?
(In reply to Ben Kohler from comment #1) > My current policy has been to always keep 2 versions for each supported > series. I'm not strictly following when they are beta versus stable > candidate versus stable. > > Is 5.10.16 not working for you? haven't applied that yet, as I only use two UAP at home I probably will never encounter any significant issue, but this pop-up as I do routine world update which force me to push forward, just a suggestion around this, relaxing this a bit may ease some management headache.
But the current policy of always keeping the 2 latest versions, eases my management headache. There was a window of about 16 hours where 5.10.12 & 5.10.15 were available, and 5.10.15 was found to have a bug. At that time, you could have downgraded to 5.10.12 if you were affected. What would be the ideal situation for you? If I'm going to keep only 2 versions per branch, should I always have latest official stable plus latest beta/candidate?
I am not strict require to follow the official workflow, as I do read the UniFi forum sometimes, there are people complain about unifi's workflow too, the 5.10.15 incident seems like they just skip the beta test, maybe just keep few more version like 3 or 4 version back is sufficient to cover most issue around this.
But by the time you realized a downgrade would help, a fixed upgrade is already available. I can drop the broken 5.10.15 ebuild and restore 5.10.12 if you like, but i'd rather not have to maintain 4 ebuilds from each branch (only 2 branches now, but it's usually 3). Another way to put it: at the time you upgraded to 5.10.15 and noticed a problem, 5.10.12 was still available for downgrade. The same commit which dropped 5.10.12 as a fallback, also added the fixed 5.10.16. I don't see a huge problem here.
How about I try to keep latest stable in each branch, plus 2 newest beta/rc, if they are newer than stable? In this case that'd mean 5.10 branch has 5.10.12 stable (to seek gentoo stable keyword soon) plus both .15 & .16 in unstable. Seem reasonable?
(In reply to Ben Kohler from comment #6) > How about I try to keep latest stable in each branch, plus 2 newest beta/rc, > if they are newer than stable? > > In this case that'd mean 5.10 branch has 5.10.12 stable (to seek gentoo > stable keyword soon) plus both .15 & .16 in unstable. > > Seem reasonable? grateful for your works, more than fair on this, I have no further question.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=439ff859f18efe8ee2daa4a843d417014a3932f6 commit 439ff859f18efe8ee2daa4a843d417014a3932f6 Author: Ben Kohler <bkohler@gentoo.org> AuthorDate: 2019-02-13 17:51:52 +0000 Commit: Ben Kohler <bkohler@gentoo.org> CommitDate: 2019-02-13 17:52:22 +0000 net-wireless/unifi: restore 5.10.12 to later target for stable kw Closes: https://bugs.gentoo.org/677884 Package-Manager: Portage-2.3.60, Repoman-2.3.12 Signed-off-by: Ben Kohler <bkohler@gentoo.org> net-wireless/unifi/Manifest | 1 + net-wireless/unifi/unifi-5.10.12.ebuild | 74 +++++++++++++++++++++++++++++++++ 2 files changed, 75 insertions(+)
While I've got you here, do you know of a page that maintains a table of current release series & their stable statuses? Right now I'm just subscribed to Unifi & Unifi Beta release blogs, which is ok but a bit hard to make sense of if I don't follow it daily.
yup, the FAQ page https://help.ubnt.com/hc/en-us/articles/360008240754#1
Perfect, thanks
