#322: New release criterion: no X libs in the minimal install set
-------------------------------+----------------------
Reporter: mattdm | Owner:
Type: enhancement | Status: reopened
Priority: major | Milestone:
Component: Release criteria | Version:
Resolution: | Keywords:
Blocked By: | Blocking:
-------------------------------+----------------------
Comment (by kparal):
Matthew, I read the document you linked, I saw that you created
http://fedoraproject.org/wiki/SIGs/Minimal_Core and I saw you started
discussion in devel list. Great job!
I think you should create some high-level goals of your SIG (e.g. "No X
libraries in the minimal system", maybe with some generic exceptions) and
FESCo should bless it. The concrete issues would be then decided by the
SIG according to this high-level goals, without bothering FESCo. This way
QA have no say in what should and what should not be included, and that is
the correct way, we don't want to have any decision powers here.
Currently we often have too much power - we create release criteria (even
though we try to get feedback from other teams), we find bugs in Fedora,
and we decide whether the bug violates the criteria. It's similar to
having a single entity to be a parliament, police and judge, all at once.
And we all know that's not a good idea.
So I'm very glad that you started the SIG. FESCo (and users of Fedora)
will decide the high level goals (the parliament), we will be the police,
and you will be the judges.
Now, the core question still remains - should we have a release criteria
matching your goals? I think we should first wait to see what requirements
you come up with and then decide whether the requirements are hard
blockers. Because we are trying to include only the important criteria
that are _critical_ to making a Fedora release. And I'm not fully sure
whether a package that got included in the minimal install and brings 10
more X libraries as dependencies is a blocker or not. I guess
cloud/rhev/similar people often use netinst/pxeboot installations and
therefore some hiccups can be fixed even after release by editing
comps.xml (comps are downloaded before installation, aren't they?).
Therefore it might not be critical to stop the release. That doesn't mean
we can't accept it as NTH and push the fix during freeze periods or
something.
I think this should get discussed when we have some tangible outputs from
your new SIG. What do you think?
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/322#comment:15>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
