ry good idea to me, Matthew.
To be clear, I wasn't speaking for anyone on the Design team, nor
trying to describe their team process. Rather I was noting that I've
observed that deadlines (which correspond to the blocker process,
obviously) have kicked up efforts on background wp. I don
nk it would make sense for the Design team to be aware of this
proposal too. I think the criterion has been used as a forcing
function in the past, so if it's not going to trigger a notification
they expect, we don't want designers to be surprised by this change in
the future.
Obviously this
ou have a feature, or fixed bug to thank for?
Probably related to:
https://bugzilla.redhat.com/show_bug.cgi?id=1161883
--
Paul W. Frieldshttp://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://
hese changes?
--
Paul W. Frieldshttp://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
--
test
On Wed, Mar 23, 2011 at 12:28:00PM -0700, Adam Williamson wrote:
> On Wed, 2011-03-23 at 12:16 -0700, Adam Williamson wrote:
> > Hey, all. I'd like to propose a special F15 schedule meeting for later
> > today or tomorrow; we'd need representation from QA and releng at a
> > minimum, ideally also d
d we should pursue a
more stringent requirement for F15 if people are amenable to that.
--
Paul W. Frieldshttp://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeo
On Fri, Oct 01, 2010 at 01:10:28PM -0700, Adam Williamson wrote:
> On Fri, 2010-10-01 at 15:58 -0400, Paul W. Frields wrote:
>
> > > I like to see that always be a requirement for the stable, stable+updates
> > > and rawhide (assuming the rawhide-pending tag becomes a re
release at "the
edge of space" through a bad push.
What if we were to graduate this requirement at the point when we have
automatic tools that give us better certainty that broken deps won't
happen except in dire circumstances?
--
Paul W. Frieldsh
intainers page, and the
> sub item about notifications should be linked to from the update_HOWTO
> and update_guidelines pages.
>
> Anybody want to take on the task of re-arranging this stuff?
Would the packaging committee be in a position to ensure this gets
done? Package maintainer do
5793074
Looks like there's an update request here. It's being requested for a
push to stable, is that applicable?
--
Paul W. Frieldshttp://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
h
stemd_package_update_breaks_default_boot_target
The QA team is going to check out what I drafted there.
>From a documentation point of view it doesn't make sense to be
updating two pages with the same detailed information about specific
issues, since they invariably will get out of sync.
--
Paul
should be:
>
> # ln -sf /lib/systemd/system/graphical.target
> /etc/systemd/system/default.target
>
> hope it's fixed now :)
I've done this, and rebooted my F14 Alpha system and it seems to work
as promised. Graphical bootup worked as it did beforehan
get
> /etc/systemd/system/default.target
>
> or
>
> # ln -sf /lib/systemd/system/multi-user.target
> /etc/systemd/system/default.target
>
> isn't it? :-)
> BTW thanks for systemd.
> Kind regards
>
> sHINOBI
> --
> devel mailing list
>
d-juicer-2.31.6-1.fc14,gnome-media-2.31.6-1.fc14,gnome-panel-2.31.6-1.fc14,totem-pl-parser-2.30.2-1.fc14
--
Paul W. Frieldshttp://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pf
14 matches
Mail list logo
