kits logic
hello devs (oleg) :)
i wonder what are the rules behind this new kit organization...
do packages from the master branch eventually make into a prime branch or are prime branches virtually immutable?
if the former, after lying into the the master branch for some time (like gentoo's stable/unstable)? how long? any other criterion instead?
if the latter, are "stable users" supposed to jump from prime-n to prime-n+1 branches at their discretion?
for example i'm on the default 5.10-prime k
packages are not flowing from master into prime branches. when new (testing) branch is created ebuilds/eclasses that creating a branch are coming from a certain snapshot of gentoo portage tree controlled by git SHA. it can be set to false, so it is not enabled by default but is available for testing, it can be set to true, when its ready to be used by default. a good thing is that users are actually allowed to do whatever they want with the branches, however the consequences might be various. wh