As you've probably heard, we're trying to get a new buildsystem ( http://hosted.fedoraproject.org/projects/koji ) in place before merging the source control. This is to give us more functionality and better resources to manage our entire distribution in the buildsystem. We're making progress with koji and are nearly there. However, I don't feel that we can swap over to Koji before the Test 3 freeze next week. To move we need to solve a few different things. A) ssl cert auth for the koji client. Work is progressing with this, but just not done yet. B) current package builds imported into the db that koji uses so that they are available for building with. This is a fairly straight forward process, but it takes time to rsync things to the new buildsystem location, import them into the db, and tag them for the correct collections. This requires a build stoppage for a period of time. C) A tool to dump the latest packages of a given collection into a repo (and potentially make it multilib) for things like pungi, extras push (for FC6), the update tool. The multilib is the hard part. Bill Nottingham has been beating on the logic around this for a bit. The other parts are fairly straight forward, the koji API is pretty easy to use. D) Makefile.common changes. I've done this before for other things, so I'll be taking this on again probably. Not too difficult, just need proper timing. Like, during the outage. E) CVS to pull packages from for build requests. We have to actually merge the content so that koji can build it. This also requires an outage and can happen during the outage that we're syncing up the latest builds and creating the tags. F) everybody to have a Fedora Account System account, the proper ACLs on their packages, and the koji client installed and properly configured. G) Storage in the colo to toss all the builds. Mike McGrath is working on this as we speak I do believe. H) Bodhi ( http://hosted.fedoraproject.org/projects/bodhi ) up and running to deliver updates for FC6 (since development inherits from the FC6 updates) I'm sure I'm forgetting some things along the way, but I think it is pretty clear that there is not a small amount of work to be done, and I'd really rather not interrupt the mad dash to get things in before the Test3 freeze, since that is the Feature Freeze as well. However after Test3 goes gold, or shortly there after, we should be able to accomplish most of the above if not all. Disadvantage is that the feature of a merged world will happen after the feature freeze, and it only gives us one more test release before the final. However with all things external, I plan to start doing more frequent public composes of things that could be downloadable. I'm doing composes almost every day anyway to test pungi code, it is just painful to sync those up to somewhere for public consumption. We could also delay Test3, and do the outage before the freeze or even during the freeze and just extend the freeze, but we'll most likely need to fix up a bunch of stuff along the way and that cuts into the time I use to get the tree in shape for release. Or we do a test5 and.... well, I don't like that idea either (: Basically I want to give people a status update on where things are going, and what work still needs to be done, and what our expectations are. I welcome input around when and how to flip the switch and whether or not dropping this "feature" in after the feature freeze is acceptable. -- Jesse Keating Release Engineer: Fedora
Attachment:
pgpxQElC8Jx8Q.pgp
Description: PGP signature
-- 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
