As part of the update acceptance policy approved by FESCo,
we have the following:

The 'important' package set is defined as the following:

* The current critical path package set
* All major desktop environments' core functionality (GNOME, KDE, XFCE,
* LXDE)
* Package updating frameworks (gnome-packagekit, kpackagekit)
* Major desktop productivity apps. An initial list would be firefox,
* kdebase (konqueror), thunderbird, evolution, kdepim (kmail).

(c.f. https://fedoraproject.org/wiki/Package_update_acceptance_criteria)

I've generated a change to the F-14 comps file along these lines.
Does this look accurate?

Bill
diff --git a/comps-f14.xml.in b/comps-f14.xml.in
index dec8d98..39d74e0 100644
--- a/comps-f14.xml.in
+++ b/comps-f14.xml.in
@@ -804,6 +804,20 @@
@core is also considered part of the Critical Path.
-->
<group>
+ <id>critical-path-apps</id>
+ <_name>Critical Path (Applications)</_name>
+ <_description>A set of applications that are considered critical path</_description>
+ <default>false</default>
+ <uservisible>false</uservisible>
+ <packagelist>
+ <packagereq type="default">evolution</packagereq>
+ <packagereq type="default">firefox</packagereq>
+ <packagereq type="default">kdebase</packagereq>
+ <packagereq type="default">kmail</packagereq>
+ <packagereq type="default">thunderbird</packagereq>
+ </packagelist>
+ </group>
+ <group>
<id>critical-path-base</id>
<_name>Critical Path (Base)</_name>
<_description>A set of packages that provide the shared platform for Critical Path functionality on all Fedora spins</_description>
@@ -839,14 +853,30 @@
<packagelist>
<!-- Just the mandatory packages from base-x. Might want to cut this
down to a small set of specific drivers in the future. -->
+ <packagereq type="mandatory">control-center</packagereq>
<packagereq type="mandatory">desktop-backgrounds-basic</packagereq>
+ <packagereq type="mandatory">fedora-gnome-theme</packagereq>
<packagereq type="mandatory">gdm</packagereq>
+ <packagereq type="mandatory">gnome-panel</packagereq>
+ <packagereq type="mandatory">gnome-session</packagereq>
+ <packagereq type="mandatory">gnome-terminal</packagereq>
+ <packagereq type="mandatory">gvfs-fuse</packagereq>
+ <packagereq type="mandatory">metacity</packagereq>
+ <packagereq type="mandatory">nautilus</packagereq>
+ <packagereq type="mandatory">polkit-gnome</packagereq>
<packagereq type="mandatory">xorg-x11-drivers</packagereq>
<packagereq type="mandatory">xorg-x11-server-Xorg</packagereq>
<packagereq type="mandatory">xorg-x11-xauth</packagereq>
<packagereq type="mandatory">xorg-x11-xinit</packagereq>
- <!-- specify this because otherwise xfce4-notifyd wins -->
+ <packagereq type="default">avahi</packagereq>
+ <packagereq type="default">gdm-plugin-fingerprint</packagereq>
+ <packagereq type="default">gdm-user-switch-applet</packagereq>
+ <packagereq type="default">gnome-packagekit</packagereq>
+ <packagereq type="default">libcanberra-gtk2</packagereq>
+ <packagereq type="default">NetworkManager-gnome</packagereq>
<packagereq type="default">notification-daemon</packagereq>
+ <packagereq type="default">pulseaudio-module-gconf</packagereq>
+ <packagereq type="default">pulseaudio-module-x11</packagereq>
</packagelist>
</group>
<group>
--
desktop mailing list
desktop@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/desktop

Am Dienstag, den 27.04.2010, 17:14 -0400 schrieb Bill Nottingham:

> <group>
> + <id>critical-path-apps</id>
> ...
> + <packagereq type="default">kdebase</packagereq>

I guess kdebase should be covered by critical-path-kde, but let's see
what the KDE comes up with after tomorrow's meeting.

Regards,
Christoph

P.S.: I'm afraid that Kevin K. declares nothing as critical so he can
happily push updates.

--
desktop mailing list
desktop@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/desktop

On Tue, 2010-04-27 at 17:14 -0400, Bill Nottingham wrote:
>
> I've generated a change to the F-14 comps file along these lines.
> Does this look accurate?
>
>

Not directly related to your question, but I think we're seeing the
critpath dep generation pick up some interesting things due to generic
provides. I think policy kit stuff was one thing where we wind up
grabbing the KDE one, and should hardcode the GNOME one instead.
Perhaps more, I have to look at the output of a critpath generation from
the proposed list.

--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
--
desktop mailing list
desktop@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/desktop

On Tue, 2010-04-27 at 17:14 -0400, Bill Nottingham wrote:
> As part of the update acceptance policy approved by FESCo,
> we have the following:
>
> The 'important' package set is defined as the following:
>
> * The current critical path package set
> * All major desktop environments' core functionality (GNOME, KDE, XFCE,
> * LXDE)
> * Package updating frameworks (gnome-packagekit, kpackagekit)
> * Major desktop productivity apps. An initial list would be firefox,
> * kdebase (konqueror), thunderbird, evolution, kdepim (kmail).
>
> (c.f. https://fedoraproject.org/wiki/Package_update_acceptance_criteria)
>
> I've generated a change to the F-14 comps file along these lines.
> Does this look accurate?

'DE core functionality' sounds vague. At this point it might be more
honest to give up the term 'critical path' and just say that everything
on the desktop live image is considered 'important'.

--
desktop mailing list
desktop@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/desktop

On Tue, 2010-04-27 at 20:19 -0400, Matthias Clasen wrote:

> 'DE core functionality' sounds vague. At this point it might be more
> honest to give up the term 'critical path' and just say that everything
> on the desktop live image is considered 'important'.

This isn't a replacement for the 'critical path', that will still exist
as a separate concept which is used for other purposes, and it has its
own clear definition. This is a new definition of an 'important' package
set, which will be used for this updates testing purpose.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net

--
desktop mailing list
desktop@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/desktop

On Wed, 2010-04-28 at 01:50 +0100, Adam Williamson wrote:
> On Tue, 2010-04-27 at 20:19 -0400, Matthias Clasen wrote:
>
> > 'DE core functionality' sounds vague. At this point it might be more
> > honest to give up the term 'critical path' and just say that everything
> > on the desktop live image is considered 'important'.
>
> This isn't a replacement for the 'critical path', that will still exist
> as a separate concept which is used for other purposes, and it has its
> own clear definition. This is a new definition of an 'important' package
> set, which will be used for this updates testing purpose.

Ah, ok. That makes more sense. But still, 'whats on the live cd' seems
like a reasonable approximation to repoclosure(core desktop + important
apps).

--
desktop mailing list
desktop@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/desktop

On Tue, 2010-04-27 at 23:31 -0400, Matthias Clasen wrote:
> On Wed, 2010-04-28 at 01:50 +0100, Adam Williamson wrote:
> > On Tue, 2010-04-27 at 20:19 -0400, Matthias Clasen wrote:
> >
> > > 'DE core functionality' sounds vague. At this point it might be more
> > > honest to give up the term 'critical path' and just say that everything
> > > on the desktop live image is considered 'important'.
> >
> > This isn't a replacement for the 'critical path', that will still exist
> > as a separate concept which is used for other purposes, and it has its
> > own clear definition. This is a new definition of an 'important' package
> > set, which will be used for this updates testing purpose.
>
> Ah, ok. That makes more sense. But still, 'whats on the live cd' seems
> like a reasonable approximation to repoclosure(core desktop + important
> apps).

I agree that the proposed wording is pretty vague, indeed, and should be
much more precise. Perhaps ask Bill about this?
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net

--
desktop mailing list
desktop@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/desktop

Christoph Wickert (christoph.wickert@googlemail.com) said:
> > <group>
> > + <id>critical-path-apps</id>
> > ...
> > + <packagereq type="default">kdebase</packagereq>
>
> I guess kdebase should be covered by critical-path-kde, but let's see
> what the KDE comes up with after tomorrow's meeting.

Per the posted policy, 'major desktop productivity apps' includes
konqueror, ergo, kdebase.

Bill
--
desktop mailing list
desktop@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/desktop

Matthias Clasen (mclasen@redhat.com) said:
> > > 'DE core functionality' sounds vague. At this point it might be more
> > > honest to give up the term 'critical path' and just say that everything
> > > on the desktop live image is considered 'important'.
> >
> > This isn't a replacement for the 'critical path', that will still exist
> > as a separate concept which is used for other purposes, and it has its
> > own clear definition. This is a new definition of an 'important' package
> > set, which will be used for this updates testing purpose.
>
> Ah, ok. That makes more sense. But still, 'whats on the live cd' seems
> like a reasonable approximation to repoclosure(core desktop + important
> apps).

Perhaps. I was thinking that while we want to give some special attention
to things like the panel, gdm, control-center, etc. that we don't
necessarily need the same attention on cheese.

Bill
--
desktop mailing list
desktop@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/desktop