F17 Beta to slip by one week.

[tox]

At the Go/No-Go meeting it was decided to slip the Beta by one week[1].
Minutes follow below.

Despite valiant efforts by many awesome people, two new blockers
appeared between RC1 and RC2, for which fixes are still incoming and
will require the creation of an RC3 [2].

As a result, ALL MAJOR MILESTONES, and their dependent tasks, will be
pushed out by one week. Beta will now be looking at an expected release
of 2012-04-10, and F17 GA is now scheduled for 2012-05-15.

The adjustments to the full F17 schedule will be done (very late)
tonight, and published to the Schedule wiki page[3]. Please note that
the high-level milestones shown on the wiki page have already been
updated to reflect the Beta slip.

Thanks for your patience. We will be meeting again next Wednesday for
another Go/No-Go meeting.

-Robyn

[1] Minutes:
http://meetbot.fedoraproject.org/fedora-meeting-1/2012-03-28/f17_beta_go_no_go_meeting.2012-03-28-21.00.html
Log:
http://meetbot.fedoraproject.org/fedora-meeting-1/2012-03-28/f17_beta_go_no_go_meeting.2012-03-28-21.00.log.html

[2] http://fedoraproject.org/wiki/Current_Release_Blockers

[3] http://fedoraproject.org/wiki/Schedule http://lists.fedoraproject.org/pipermail/devel/2012-March/165082.html


Note: im not gonna bother posting RC2 since its been said to be Buggy

[nonamedotc]

I was going to post that RC2 was not available, but now that this is up, I think RC2 post would be meaningless. It might make more sense to test beta directly instead of RC1.

[tox]

i did post RC2 links but there in the RC1 thread, but shhh dont tell anyone

[tox]

At the Go/No-Go meeting it was decided to slip the Beta by an additional
week[1]. Minutes follow below.

Though the QA team was able to get through all validation testing, it
was found that preupgrade was not functioning at an acceptable level,
thus becoming an additional blocker which prevents us from shipping RC3,
and necessitating the creation of an RC4.

As a result, ALL MAJOR MILESTONES, and their dependent tasks, will be
pushed out by one week. Beta will now be looking at an expected release
of 2012-04-17, and F17 GA is now scheduled for 2012-05-22. This is the
second one-week slip of beta.

Adjustments to the full F17 schedule have been completed and now reflect
the above Beta and GA dates, and high-level milestones have been updated
as well on the Schedule wiki page[3].

We will be meeting again next Wednesday for another Go/No-Go meeting
(2012-04-11.) All hail our QA pals and the anacondanistas for their
dedication (and many, many others as well).

-Robyn

[1] Minutes:
http://meetbot.fedoraproject.org/fedora-meeting-1/2012-04-05/gono-go_continuation_f17_beta_rc3_part_two_or_three.201 2-04-05-15.00.html

Logs:
http://meetbot.fedoraproject.org/fedora-meeting-1/2012-04-05/gono-go_continuation_f17_beta_rc3_part_two_or_three.201 2-04-05-15.00.log.html

[2] http://fedoraproject.org/wiki/Current_Release_Blockers

[3] http://fedoraproject.org/wiki/Schedule


Minutes:

================================================== ===========
#fedora-meeting-1: Go/No Go Continuation, Round Two, RC3, F17
================================================== ===========


Meeting started by rbergeron at 15:00:38 UTC. The full logs are
available at
http://meetbot.fedoraproject.org/fedora-meeting-1/2012-04-05/gono-go_continuation_f17_beta_rc3_part_two_or_three.201 2-04-05-15.00.log.html
.



Meeting summary
---------------
* Who's up (rbergeron, 15:01:03)

* Test Results (rbergeron, 15:11:31)
* LINK:
https://fedoraproject.org/wiki/Test_Results:Fedora_17_Beta_RC3_Install
(rbergeron, 15:11:37)
* LINK:
https://fedoraproject.org/wiki/Test_Results:Fedora_17_Beta_RC3_Base
(rbergeron, 15:12:11)
* LINK:
https://fedoraproject.org/wiki/Test_Results:Fedora_17_Beta_RC3_Desktop
(rbergeron, 15:12:22)
* AGREED: we are okay with the level of test coverage as of now on RC3
(rbergeron, 15:16:31)

* Blockers (rbergeron, 15:16:41)

* https://bugzilla.redhat.com/show_bug.cgi?id=741594 (adamw, 15:18:19)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=741594#c14
(Martix, 15:18:54)
* AGREED: 741594 does not hit any of the criteria and the cited
scenarios are not significant enough to worry about delaying the
beta (adamw, 15:29:18)

* https://bugzilla.redhat.com/show_bug.cgi?id=810226 (adamw, 15:31:12)
* LINK: http://patchwork.freedesktop.org/patch/9198/ (adamw,
15:40:55)

* https://bugzilla.redhat.com/show_bug.cgi?id=810161 (adamw, 15:48:57)
* AGREED: 810161 is rejected as a blocker because the impact is minor
(it's essentially a cosmetic bug, desktop is still usable), also it
only hits one specific virt configuration so it can at least be
worked around. accepted as NTH and will be commonbugs'ed if we ship
with it (adamw, 16:13:56)

* https://bugzilla.redhat.com/show_bug.cgi?id=810289 (adamw, 16:14:24)
* AGREED: #810289 is rejected as a blocker on the basis that we've
never actually checked for low space on upgrade (and hence have
implictly never considered it a blocking issue). anaconda will just
try to upgrade and explode. so this isn't in fact a regression
compared to earlier releases, and we don't have a specific
requirement for a low space check in criteria or anywhere else.
accepted as NTH (adamw, 16:31:38)

* https://bugzilla.redhat.com/show_bug.cgi?id=810136 (adamw, 16:31:59)
* AGREED: 810136 turns out to be a dupe of 810005, moving discussion
(adamw, 19:45:37)

* https://bugzilla.redhat.com/show_bug.cgi?id=810005 (adamw, 19:45:42)
* AGREED: 810005 is accepted as a blocker per criterion "The installer
must be able to successfully complete an upgrade installation from a
clean, fully updated default installation (from any official install
medium) of the previous stable Fedora release, either via preupgrade
or by booting to the installer manually. The upgraded system must
meet all release criteria". the known workaround has too many
limitations to be considered 'good enough' (adamw, 19:53:23)

* Go or no-go? (rbergeron, 19:54:12)
* we have a blocker. (rbergeron, 19:54:27)
* qa votes no-go, as do various others from engineering, fesco, pm
(rbergeron, 19:55:18)
* AGREED: we are no-go on F17 Beta RC3 sadly (adamw, 19:58:27)
* ACTION: rbergeron to update schedule.... again (rbergeron,
19:58:55)
* ACTION: rbergero to send slip mail (rbergeron, 20:00:19)
* ACTION: tflink to do blocker meeting mail following slip notice
(rbergeron, 20:00:38)
* ACTION: qa heroes of awesome to get some rest plz (rbergeron,
20:03:09)
* ACTION: adamw to get a hole in one (rbergeron, 20:03:23)
* we will re-convene tomorrow or monday (adamw, 20:08:56)

Meeting ended at 20:08:59 UTC.




Action Items
------------
* rbergeron to update schedule.... again
* rbergero to send slip mail
* tflink to do blocker meeting mail following slip notice
* qa heroes of awesome to get some rest plz
* adamw to get a hole in one




Action Items, by person
-----------------------
* adamw
* adamw to get a hole in one
* rbergeron
* rbergeron to update schedule.... again
* tflink
* tflink to do blocker meeting mail following slip notice
* **UNASSIGNED**
* rbergero to send slip mail
* qa heroes of awesome to get some rest plz




People Present (lines said)
---------------------------
* adamw (360)
EDITOR'S NOTE: Dude! It's like 360 degrees of adamw :)
* wwoods (99)
* rbergeron (91)
* tflink (56)
* bcl (54)
* nirik (49)
* Kevin_Kofler (37)
* ajax (32)
* Martix (19)
* rdieter_work (8)
* zodbot (6)
* cpuobsessed (5)
* pjones (5)
* ianweller (4)
* kalev (3)
* spot (3)
* satellit_laptop (1)
* pschindl_ (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot


F17 Beta to slip by an additional week.

as they say The Tradition Continues :rtfl:

---------- Post added at 09:07 AM ---------- Previous post was at 09:06 AM ----------

http://lists.fedoraproject.org/pipermail/devel/2012-April/165472.html

[gman1]

I am not sure the best place to post this, but here goes....

I have been testing fedora 17 destop/xfcx live nightlys/alphas/betas iso's since January....
I have not gotten ANY of them to work since 01/20/2012 nightly(I think that was the date - definately january 20ish).... And I have downloaded almost ALL since then....

It gets pretty close to loading.... the 'F' Loading symbol graphic goes most of the way through.... Then when it is time to bring up the Login screen - it just goes BLACK and LOCKS.... I am currently using fedora 16 xfce with all the current updates/kernels with no problem.... So I am guessing something has changed in the boot between 16 and 17????

I have a HP Pavilion g series notebook:
althonII-P360
ati/RadeonHD4250
4gb/ddr3/1.0ghz
64g corsair nova ssd
sb-Azalia

better late than never with this post.... I thought for sure this would have been fixed before we got this close to releasing the beta version....

ps: I have been loading the live iso's from USB sticks(not an actual cd/dvd)....

[Dan]

Have you filed a bug report on this? There's no way for the developers to know you've uncovered an issue if you don't file a report on it.

[AndrewSerk]

I downloaded the F17 beta i686 live desktop from the 4th the other night. It boots and installs just fine here.

[Dan]

Try scrolling with the mouse wheel in nautilus.

[AndrewSerk]

Try scrolling with the mouse wheel in nautilus.

Well that is a unexpected function! :p Goes to the end no matter what way I scroll.

[Dan]

Ayup.

http://forums.fedoraforum.org/showthread.php?t=278544

[gman1]

Have you filed a bug report on this? There's no way for the developers to know you've uncovered an issue if you don't file a report on it.

I looked through the bug reports, and did not find a match.... I can't really give any more detail about the problem, other that what I have said here - so I don't think it would be very helpful....

I didn't open a bug report myself, because they need a persons email address - that will be displayed publicly, and very easily seen, and spammed.... So they don't make it easy to report bugs....

[Dan]

Okey dokey. Your choice. But the bottom line remains the same. Unless somebody else has exactly the same hardware, and exactly the same problem, and does make that committment to the open source community, the developers will never know there is a problem, and therefore it's a crapshoot whether it will ever get fixed.

That being said, it's also quite likely you have a video driver problem. But without the help of the developers, you're kind of on your own to hunt up a solution here on the forums and elsewhere.

And for what it's worth ... My gmail address is readily visible when I file bug reports, but I've never been spammed by anyone from RedHat Bugzilla. I think. But then again, Gmail does a remarkable job of filtering that kind of crud out before I ever have to see it. A gmail throw-away account can be an awfully handy thing to have. <..;)..>

[tox]

I looked through the bug reports, and did not find a match.... I can't really give any more detail about the problem, other that what I have said here - so I don't think it would be very helpful....

I didn't open a bug report myself, because they need a persons email address - that will be displayed publicly, and very easily seen, and spammed.... So they don't make it easy to report bugs....

use a throw-away kinda email address, not a personal one to file a Bug report

[DBelton]

I looked through the bug reports, and did not find a match.... I can't really give any more detail about the problem, other that what I have said here - so I don't think it would be very helpful....

I didn't open a bug report myself, because they need a persons email address - that will be displayed publicly, and very easily seen, and spammed.... So they don't make it easy to report bugs....

Have you tried editing your kernel line when you boot, and remove the rhgb and quiet options so you can see more about what is happening?

also, add the following 2 kernel parameters to get a little more debug information if the above doesn't help

systemd.log_level=debug
systemd.log_target=kmsg


Also, I have never gotten spam due to my email address being available on bugzilla.

[bob]

Gman, we've both been around since '04 and I also hate bugzilla's flaws, but I continue to file them: 1). Because if I'm a Beta tester that has chosen to install something before "final", I'm really agreeing to provide feedback. 2). Because I want to provide humor to the Devs when they sit around passing idiot messages at a company function. :D

However, I've never been spammed by anything or anyone as a result. Gotta believe that if we're talented enough to deal with 'cutting-edge-distro-betas', we're not the target they're after.

[gman1]

Have you tried editing your kernel line when you boot, and remove the rhgb and quiet options so you can see more about what is happening?

also, add the following 2 kernel parameters to get a little more debug information if the above doesn't help

systemd.log_level=debug
systemd.log_target=kmsg


Also, I have never gotten spam due to my email address being available on bugzilla.

yes I tried that everything comes up [ ok ].... It happend when the login screen should appear.... I just get a black screen, and lockup....

there is no way to get a log file on a live usb stick boot is there????

---------- Post added at 09:32 AM ---------- Previous post was at 09:30 AM ----------

use a throw-away kinda email address, not a personal one to file a Bug report


I am not afraid to be spammed by fedora users, I am afraid to get my email address on some span list from some spam collecting BOT.... I used to be on there with a throw away email address, but don't have it any more....

I will spare you my long story about my spam email experiences.... If everyone is using bogus email accounts, than why do sites like bugzilla even bother to show them to everyone....

---------- Post added at 10:47 AM ---------- Previous post was at 09:32 AM ----------

Have you filed a bug report on this? There's no way for the developers to know you've uncovered an issue if you don't file a report on it.

OK I have reported the bug with a junk email address

link: https://bugzilla.redhat.com/show_bug.cgi?id=810888

thanks everyone....

[smr54]

For what it's worth, you only see other email addresses if you are logged in.

Which certainly doesn't make it invulnerable, but it does help.

[tox]

gman1

take your complaints to the Bugzilla devs.. ( that being Mozilla devs that make Bugzilla ) i use my personal email address an i have never been spammed from anyone from redhat bugzilla.