3:58 p.m.
#5385: Request push systemd-195-2.fc18 through the freeze
----------------------------+------------------------
Reporter: johannbg | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 18 Beta | Component: other
Keywords: | Blocked By:
Blocking: |
----------------------------+------------------------
Given that this [1] update is an automatic blocker since fedup is depend
on [2] thus it breaks
"For each one of the release-blocking package sets ('minimal', and the
package sets for each one of the release-blocking desktops), it must be
possible to successfully complete an upgrade from a fully updated
installation of the previous stable Fedora release with that package set
installed, using any officially recommended upgrade mechanisms. The
upgraded system must meet all release criteria."
I here by request that releng pushes systemd-195-2 through the freeze...
1.https://admin.fedoraproject.org/updates/FEDORA-2012-16709/systemd-195-2...
2.https://github.com/wgwoods/fedup-dracut/blob/master/fedup-dracut.spec
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5385>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
5:23 p.m.
#5385: Request push systemd-195-2.fc18 through the freeze
-----------------------------+-----------------------
Reporter: johannbg | Owner: rel-eng@…
Type: task | Status: closed
Milestone: Fedora 18 Beta | Component: other
Resolution: invalid | Keywords:
Blocked By: | Blocking:
-----------------------------+-----------------------
Changes (by rdieter):
* resolution: => invalid
* status: new => closed
Comment:
(correct me if I'm wrong, but...) this isn't releng's job to decide or
implement this.
QA has a clear process that during freezes (like now), only fixes for
blocker bugs will be accepted,
http://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
So, I suggest you file a bug, nominate is blocker, and if QA accepts it,
it'll get pulled in.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5385#comment:1>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
6:56 p.m.
#5385: Request push systemd-195-2.fc18 through the freeze
-----------------------------+-----------------------
Reporter: johannbg | Owner: rel-eng@…
Type: task | Status: closed
Milestone: Fedora 18 Beta | Component: other
Resolution: invalid | Keywords:
Blocked By: | Blocking:
-----------------------------+-----------------------
Comment (by mattdm):
Can't NTH (Nice-To-Have) bugs also get past the freeze?
http://fedoraproject.org/wiki/QA:SOP_nth_bug_process
I would consider a number of the bugs fixed here *seriously* "nice to
have".
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5385#comment:2>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
6:41 a.m.
#5385: Request push systemd-195-2.fc18 through the freeze
-----------------------------+-----------------------
Reporter: johannbg | Owner: rel-eng@…
Type: task | Status: closed
Milestone: Fedora 18 Beta | Component: other
Resolution: invalid | Keywords:
Blocked By: | Blocking:
-----------------------------+-----------------------
Comment (by jwboyer):
Replying to [comment:2 mattdm]:
Can't NTH (Nice-To-Have) bugs also get past the freeze?
http://fedoraproject.org/wiki/QA:SOP_nth_bug_process
I would consider a number of the bugs fixed here *seriously* "nice to
have".
Then they need to go through the actual QA process QA has in place.
Nothing in the SOP you linked to suggests opening a rel-eng ticket and
going around the QA team.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5385#comment:3>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
7:08 a.m.
#5385: Request push systemd-195-2.fc18 through the freeze
-----------------------------+-----------------------
Reporter: johannbg | Owner: rel-eng@…
Type: task | Status: closed
Milestone: Fedora 18 Beta | Component: other
Resolution: invalid | Keywords:
Blocked By: | Blocking:
-----------------------------+-----------------------
Comment (by johannbg):
Replying to [comment:1 rdieter]:
(correct me if I'm wrong, but...) this isn't releng's job
to decide or
implement this.
QA has a clear process that during freezes (like now), only fixes for
blocker bugs
will be accepted,
http://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
So, I suggest you file a bug, nominate is blocker, and if QA accepts it,
it'll
get pulled in.
Oh really what more information about the QA community would you like to
relay to me?
Did adamw put you up to this because he did not get to ping nirik og
dgilmore on irc to bypass all transparency and work flow in doing so?
Or is this just general because it was not filed by the Red Hat's QA team
we will not do it?
This already was mentions and discussed on last QA meeting along with on
https://bugzilla.redhat.com/show_bug.cgi?id=871161
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5385#comment:4>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
7:20 a.m.
#5385: Request push systemd-195-2.fc18 through the freeze
-----------------------------+-----------------------
Reporter: johannbg | Owner: rel-eng@…
Type: task | Status: closed
Milestone: Fedora 18 Beta | Component: other
Resolution: invalid | Keywords:
Blocked By: | Blocking:
-----------------------------+-----------------------
Comment (by jwboyer):
Replying to [comment:4 johannbg]:
Replying to [comment:1 rdieter]:
> (correct me if I'm wrong, but...) this isn't releng's job to decide or
implement this.
>
> QA has a clear process that during freezes (like now), only fixes for
blocker
bugs will be accepted,
> http://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
Did adamw put you up to this because he did not get to ping nirik og
dgilmore on
irc to bypass all transparency and work flow in doing so?
No.
Or is this just general because it was not filed by the Red Hat's
QA
team we will not do it?
No.
This already was mentions and discussed on last QA meeting along with
on
https://bugzilla.redhat.com/show_bug.cgi?id=871161
If you had mentioned that bug to begin with it would have saved everyone a
lot of time.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5385#comment:5>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
7:32 a.m.
#5385: Request push systemd-195-2.fc18 through the freeze
-----------------------------+-----------------------
Reporter: johannbg | Owner: rel-eng@…
Type: task | Status: closed
Milestone: Fedora 18 Beta | Component: other
Resolution: invalid | Keywords:
Blocked By: | Blocking:
-----------------------------+-----------------------
Comment (by mattdm):
Replying to [comment:3 jwboyer]:
Replying to [comment:2 mattdm]:
> Can't NTH (Nice-To-Have) bugs also get past the freeze?
http://fedoraproject.org/wiki/QA:SOP_nth_bug_process
Then they need to go through the actual QA process QA has in place.
Nothing in the SOP you linked to suggests opening a rel-eng ticket and
going around the QA team.
I wasn't suggesting otherwise — just noting that the process also includes
nice-to-have, not just hard blockers.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5385#comment:6>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
7:56 a.m.
#5385: Request push systemd-195-2.fc18 through the freeze
-----------------------------+-----------------------
Reporter: johannbg | Owner: rel-eng@…
Type: task | Status: closed
Milestone: Fedora 18 Beta | Component: other
Resolution: invalid | Keywords:
Blocked By: | Blocking:
-----------------------------+-----------------------
Comment (by johannbg):
If you had mentioned that bug to begin with it would have saved
everyone
a lot of time.
Lack of proper communication seems to be the theme of this release cycle
:)
It may be acceptable by Adam and perhaps Red Hat in general to handle
these kind of things by irc personal mail or through some various chat
clients but it's certainly not acceptable for a whole community where
*anybody* from within the community can file an request for an push
through freeze. I'm going come up with and write SOP for QA Community to
have a firm work flow for the community to follow so
transparency,traceability between those two community are in place.
Meanwhile you guys just have to start to accept the fact that Adam wont be
the only one handling these issues in the future...
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5385#comment:7>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
8:55 a.m.
#5385: Request push systemd-195-2.fc18 through the freeze
-----------------------------+-----------------------
Reporter: johannbg | Owner: rel-eng@…
Type: task | Status: closed
Milestone: Fedora 18 Beta | Component: other
Resolution: invalid | Keywords:
Blocked By: | Blocking:
-----------------------------+-----------------------
Comment (by rdieter):
Your accusations... are at best offbase. Besides, bug #871161 is not yet
marked as AcceptedBlocker, so filing here is (still) premature.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5385#comment:8>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
9:17 a.m.
#5385: Request push systemd-195-2.fc18 through the freeze
-----------------------------+-----------------------
Reporter: johannbg | Owner: rel-eng@…
Type: task | Status: closed
Milestone: Fedora 18 Beta | Component: other
Resolution: invalid | Keywords:
Blocked By: | Blocking:
-----------------------------+-----------------------
Comment (by johannbg):
Replying to [comment:8 rdieter]:
Your accusations... are at best offbase.
Given that you have been here with the project long enough and you are
well educated man thus you are aware of the fact that history repeats
itself I'm interesting to hear what you mean by my accusation are at best
offbase...
Besides, bug #871161 is not yet marked as AcceptedBlocker, so filing
here is (still) premature.
As you wish let's wait for the meeting I seriously doubt that there is any
new info that has not already been discussed before and the reason this
was not an already an blocker is because we have not been able up to this
point to properly test the upgrade tool heck i'm not sure if it has passed
it's packaging review yet hence we have needed to punt this along with
other upgrade related bugs until it became available.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5385#comment:9>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
12:34 p.m.
#5385: Request push systemd-195-2.fc18 through the freeze
-----------------------------+-----------------------
Reporter: johannbg | Owner: rel-eng@…
Type: task | Status: closed
Milestone: Fedora 18 Beta | Component: other
Resolution: invalid | Keywords:
Blocked By: | Blocking:
-----------------------------+-----------------------
Comment (by johannbg):
"Discussed at 2012-10-31 blocker review meeting:
http://meetbot.fedoraproject.org/fedora-qa/2012-10-31/f18beta-blocker-
review-6.2012-10-31-16.00.log.txt . Agreed that as the process by which
upgrade.img will be built and shipped(?) is still not clear we cannot be
sure if this actually needs to block the Beta release, but there is a
possibility that it might, and in that case, we should pull the fix
immediately so we have time to test it, rather than realizing we need it
later on and not having time to test it properly.
Therefore the issue is accepted as NTH and we leave the blocker question
open, to be determined later if required. This gives us flexibility to
take the systemd update now, but back it out again if testing indicates it
is broken and we determine we don't actually need it for fedup."
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5385#comment:10>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
12:41 p.m.
#5385: Request push systemd-195-2.fc18 through the freeze
-----------------------------+-----------------------
Reporter: johannbg | Owner: rel-eng@…
Type: task | Status: reopened
Milestone: Fedora 18 Beta | Component: other
Resolution: | Keywords:
Blocked By: | Blocking:
-----------------------------+-----------------------
Changes (by rdieter):
* resolution: invalid =>
* status: closed => reopened
Comment:
finally :)
https://admin.fedoraproject.org/updates/FEDORA-2012-16709/systemd-195-2.fc18
is the one to pull in.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5385#comment:11>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
12:43 p.m.
#5385: Request push systemd-195-2.fc18 through the freeze
-----------------------------+-----------------------
Reporter: johannbg | Owner: rel-eng@…
Type: task | Status: reopened
Milestone: Fedora 18 Beta | Component: other
Resolution: | Keywords:
Blocked By: | Blocking:
-----------------------------+-----------------------
Comment (by rdieter):
though stictly speaking, that update isn't marked as fixing or unblocking
the bug referenced here earlier, 871161 (should it be added?).
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5385#comment:12>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
10:17 a.m.
#5385: Request push systemd-195-2.fc18 through the freeze
-----------------------------+-----------------------
Reporter: johannbg | Owner: rel-eng@…
Type: task | Status: closed
Milestone: Fedora 18 Beta | Component: other
Resolution: fixed | Keywords:
Blocked By: | Blocking:
-----------------------------+-----------------------
Changes (by kevin):
* resolution: => fixed
* status: reopened => closed
Comment:
done.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5385#comment:13>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
4192
days inactive
4194
days old
rel-eng@lists.fedoraproject.org
13 comments
1 participants
participants (1)
-
Fedora Release Engineering