On Wed, 9 Feb 2022 at 18:15, Kevin Fenzi <kevin@xxxxxxxxx> wrote: > > On Wed, Feb 09, 2022 at 06:26:44PM +0100, Fabio Valentini wrote: > > On Wed, Feb 9, 2022 at 6:12 PM Jonathan Wakely <jwakely@xxxxxxxxxx> wrote: > > > > > > On Tue, 8 Feb 2022 at 20:40, Tomas Hrcka <thrcka@xxxxxxxxxx> wrote: > > > > > > > > Hi All, > > > > > > > > Fedora 36 has now been branched, please be sure to do a git pull > > > > --rebase to pick up the new branch, as an additional reminder > > > > rawhide/f36 has been completely isolated from previous releases, so > > > > > > What does this mean? > > > > > > > this means that anything you do for f36 you also have to do in the > > > > rawhide branch and do a build there. > > > > > > Right, f36 is a separate branch from rawhide now. That makes sense. > > > What does "rawhide/f36 has been completely isolated from previous > > > releases" mean? If it's trying to say "rawhide and f36 are now > > > separate branches" it fails to do so. Is it supposed to say > > > rawhide/f37? > > > > Yeah, that template sounds really archaic by todays standards, and > > it's at least misleading or even wrong in some regards. > > So it could benefit from being updateg ... Is it maintained in a > > public repo somewhere where one could submit a PR to fix it? :) > > Well, it means _builds_ are not inherited between them. > > Long ago we used to let branched inherit into rawhide until there was a > branched build. This turned out to cause a number of problems so we > stopped doing it. So now if you do a f36 build, you need to also make > sure to do a f37 one as well. I can't see how "rawhide/f36 has been completely isolated from previous releases" can be interpreted to mean that :-) f36 was already isolated from f35 and the other previous releases. rawhide has now been isolated from f36 (which is not a release). How about rewording it as: "Fedora 36 has now been branched, please be sure to do a git fetch to pick up the new branch. As f36 and rawhide are now separate branches, anything you do for f36 must also be done in the rawhide branch." (This seems backwards for my workflow. If I wanted to make a change on both rawhide and f36 I'd do it in rawhide and do a fast-forward merge to get it on the f36 branch, but this announcement probably isn't the place to be giving people tips on git workflow.) The next part seems OK ... "There will be a Fedora 36 compose and it'll appear in http://dl.fedoraproject.org/pub/fedora/linux/development/36/ once complete. Please be sure to check it out." Although I'd avoid the contraction "it'll" and I'm not sure what "check it out" means. Is it telling me to checkout a Git branch? Because that's how it could be interpreted. I think it's telling me to try the 36 compose. "Please be sure" sounds like this is something I *should* be doing as a package maintainer, but I'm afraid I never routinely try pre-release composes. Maybe it should simply encourage people to try it, not sound like it's compulsory. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
