On Sun, May 10, 2015 at 1:28 PM, Dennis Gilmore <dennis(a)ausil.us> wrote:
Hi all,
As we get closer to the FAD we need to nail down the deliverables and what we
want to achieve by the end of the FAD. I am going to list some of the things
I think we need to have done. feel free to discuss and add things. at the ned
we will update the wiki with the deliverables.
1) working pungi 4.
2) integrated ability to make atomic installer and pxe to live in pungi
3) mash ported to createrepo_c
4) rawhide looking like a TC/RC
5) bodhi2 able to trigger atomic installer and pxe to live as part of the
update push process.
6) livemedia-creator koji integration
7) koji able to manage the url line in kickstarts so that we can do real
builds
8) run-root plugin configured
9) Secondary arches working exactly teh same as primary
10) port pungi to dnf
11) make headway and plan to port to python 3
Before the FAD, we need to work with infrastructure and have a plan for the
support of pagure for git repo hosting.
A big thing we must have to support being flexible in delivery going forward
is bodhi 2. Without it we can not deliver atomic in the way that atomic
desires.
One other thing I've been thinking of recently that I'm surprised
hasn't been getting a lot of discussion is Fedora.Next[0], are there
any requirements with the "Rings" and/or "Environments and Stacks"
that we need to address in the near term with current tooling as well
as take into account for next-gen tooling design?
Has any of this been officially defined? If so, where is that all
written down. If not, can we start sorting that out?
I feel like if we don't have a clean formal definition of these things
we're just going to attempt to address the vague goal of building
container images to publish $somewhere for $reasons.
-AdamM
[0] -
https://fedoraproject.org/wiki/Fedora.next
Dennis
_______________________________________________
rel-eng mailing list
rel-eng(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/rel-eng