2018-07-26 16:04 GMT+03:00 Rich Freeman <ri...@gentoo.org>: > On Thu, Jul 26, 2018 at 8:45 AM Grand Duet <grand.d...@gmail.com> wrote: >> > Did this even impact the stable branch? >> >> Yes. > > Hmm, I suspect I didn't sync before it was reverted. Either that or I > noticed the noise on the lists and waited a day. > > This is one issue with our news - it isn't really realtime. If we > want people to hold the presses and re-sync they don't get that notice > until they've already re-synced. > >> May be, adding some additional "almost stable" level between >> "stable" and "unstable" one to make "stable" stable indeed? > > If anything it seems like the proposal to drop stable comes along > every few years. I don't see anybody being eager to add another level > of QA. A big practical issue would be that unless people are actually > using the two lower levels significantly then nothing is actually > getting checked before going to stable. > > There is really no reason you couldn't have a release-based Gentoo > derivative. Everything is in git. All "somebody" needs to do is > start a repo with a release-driven workflow that treats Gentoo as the > upstream master branch, targeting changes for release branches and > then doing release candidates and QA/etc. Then those release-based > users would sync from there instead of the upstream Gentoo repo. > Ideally somebody would bundle it with a reference binary repo that > people could optionally sync from to speed installs for packages where > they're not changing USE flags. > > The problem is that this all takes quite a bit of work, and I'm > skeptical that it would ever happen. However, for larger Gentoo > deployments in production environments I suspect most are doing things > more-or-less in this fashion, but just with the packages they care > about. If somebody has 100 production servers running Gentoo I doubt > they are set to just sync from us. Rather they would set up their own > mirror and carefully test portage snapshots before they go rolling > them out.
Ok. Thank you for your reply.
