On Monday 07 May 2007, Jesse Keating wrote: > On Monday 07 May 2007 16:42:49 Ville Skyttä wrote: > > > Presumably the maintainer knew that they were breaking upgrade path > > > when doing the FE6 build, and thus did a build on devel/. > > > > Well, I didn't until an hour or so ago. And looks like I'm not the only > > one who missed it. > > Er, using koji doesn't change this at all. You built something on FC-6/ > branch. It may have a higher NVR than the last thing you built on devel/, > therefor you need to do a build on devel/. That should all be the same and > there should be a build done on devel/. The only missing part _now_ is > asking for that already done build on devel/ be tagged for f7-final. Sure. It appears I misread your sentence quoted above, but nevermind. I think the tag names are the things that misled me; I thought f7-final == set of packages that are in F7 the day it is released (pretty self explanatory tag name), and dist-f7 == set of packages that get automatically rolled into F7 repositories as updates after the release or something, but definitely included anyway - "dist-f7" expands naturally into "distributed in F7" or "part of the F7 distribution" when I read it. So now my understanding is that dist-f7 is not the above, but rather kind of a queue for builds possibly to be included in F7 later based on some criteria, primarily if the maintainer asks and rel-eng approves. I think I wouldn't have been nearly that confused if dist-f7 would have been called eg. f7-queue, f7-candidate, f7-pending or something along those lines. -- Fedora-maintainers mailing list Fedora-maintainers@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers -- Fedora-maintainers-readonly mailing list Fedora-maintainers-readonly@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly
