Feodra 13 Alpha slip by one week
by Jesse Keating
Today at the go / no-go meeting[1] we decided to slip the Alpha by one
week. This slip is needed to verify blocker bug fixes and validate new
builds of software necessary to fix those bugs. We are confident that
the fixes we have are valid, however we do not have enough time to prove
them valid. We will spend the next few days doing that validation. In
the mean time builds will continue to be pushed to updates-testing for
13, and even to 13 stable, however critical path packages might not be
pushed unless they are fixing a release blocking issue. Once we've
validated all the fixes we will do more frequent pushes to 13 stable.
At this time we are not adjusting later milestone dates, as with no
frozen rawhide we are not taking away any developer time.
[1]:
http://meetbot.fedoraproject.org/fedora-meeting/2010-02-25/fedora-meeting...
--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
13 years, 3 months
Fedora 13 Alpha Go/No-Go Meeting RESCHEDULED: 2010-02-25 @ 19:00 UTC (14:00 EST)
by Adam Williamson
IMPORTANT NOTE: we are rescheduling the Go/No-Go meeting for Fedora 13
Alpha. Previously scheduled for 2010-02-25 01:00 UTC, it is now
scheduled for 2010-02-25 19:00 UTC (14:00 EST, 11:00 PST). This delay is
to give sufficient time for the QA team to test the expected RC3 build.
The original announcement, with the new time, is reproduced below for
reference.
Join us on irc.freenode.net #fedora-meeting for this important meeting.
Thursday, February 25, 2010 @ 19:00 UTC (14:00 EST).
"Before each public release Development, QA, and Release Engineering
meet to determine if the release criteria are met for a particular
release. This meeting is called the: Go/No-Go Meeting."
"Verifying that the Release criteria are met is the responsibility of
the QA Team."
For more details about this important meeting see:
https://fedoraproject.org/wiki/Engineering_Readiness_Meetings
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
13 years, 3 months
Call for F13 release slogan suggestions
by Robyn Bergeron
Greetings Friends,
We need a slogan for the F13 release. It will be chosen one week from
now, on 3/2. A release slogan is a short call-to-action that fits the
artwork theme from Design, found at
https://fedoraproject.org/wiki/F13_release_slogan#Themes. (F12's
slogan was "Unite.")
If you are interested in suggesting ideas for the release slogan,
please take a look at the Release Slogan SOP, and the criteria for
selection, at https://fedoraproject.org/wiki/Release_slogan_SOP. The
slogan must be:
* short (1-3 words)
* a call to action
* positive
It should reinforce that Fedora helps the user achieve something
great. It should also reflect some of ideas and themes found in the
release artwork, and, if possible, also touch upon the Four
Foundations (http://https://fedoraproject.org/wiki/Foundations).
Please put your slogan ideas here:
https://fedoraproject.org/wiki/F13_release_slogan#New_slogan_ideas
The deadline for submissions is Tuesday 3/2 at 20:00 UTC, which is our
next Marketing meeting
(https://fedoraproject.org/wiki/Marketing_meetings). We'll be
discussing submissions there, and then the FPL, Mo Duffy, and the
Marketing team lead will take that input and select the final slogan
on 3/2, following the marketing meeting. Let me know if you have any
questions, comments, or concerns -- and let the wiki table know if you
have any ideas!
Cheers,
Robyn
13 years, 3 months
Read this if your package BuildRequires qt(4)-devel!!!
by Kevin Kofler
Hi,
for all maintainers of packages which BuildRequire qt4-devel (or qt-devel, but
the versioned virtual Provides is preferred): please, when you plan to push
updates for your packages, ALWAYS CHECK what version of Qt your package got
built against and DO NOT PUSH your update to stable before that version of Qt
goes stable! A package built against Qt 4.6 WILL NOT WORK AT ALL with Qt
4.5!!! (This is always the case, Qt is backwards- but not forwards-
compatible.)
Currently, buildroot overrides for Qt 4.6 are in effect (intermittently, as Qt
4.6 can and will be untagged from the buildroot on request to build updates
which need to go out soon, but we need it in the buildroot to build anything
related to KDE 4.4), so a package built now CANNOT go to stable before the big
Qt 4.6 / KDE 4.4 / SIP 4.10 update does. If you need to push an urgent update,
please ask Rex Dieter (rdieter on Freenode IRC) or another rel-eng member to
get the stuff out of the buildroot for a moment, and follow the instructions
given on IRC. If your update is not urgent, I recommend just not pushing it
out to stable before the big Qt/KDE/SIP update.
NOT FOLLOWING THOSE INSTRUCTIONS WILL LEAD TO YOUR PACKAGE BEING BROKEN IN THE
STABLE UPDATES!!! YOU HAVE BEEN WARNED!
I am sorry if I sound abrasive, but we already had at least 2 packages which
were broken due to this issue (just for 4.6, there were more such issues with
previous upgrades) and it looks like our previous devel-announce message was
not clear enough. Please double-check before you hit that "push to stable"
button! Thanks in advance.
We will look into using some less dangerous process (special build tags?) for
future Qt updates as this is just not working, but for now please be careful.
Kevin Kofler
13 years, 3 months
Call for Participation - Fedora 13 Talking Points
by Robyn Bergeron
Talking points are key highlights of the new release. They should be
compelling, but they will not necessarily be comprehensive. There are
different types of talking points for different types of people:
general desktop users/everyone, developers, and sysadmins. For the
Fedora 13 cycle, we will also have talking points to address some of
the Spins. They are meant to provide a short, effective answer to the
question, "What cool stuff is in the latest release of Fedora?"
Each cycle, the Marketing team compiles a short list of approximately
three talking points for each of these audiences for the upcoming
release. For Fedora 13, they're found here:
https://fedoraproject.org/wiki/Fedora_13_Talking_Points
If you have a talking point that you feel meets the criteria found on
the talking points SOP page at
https://fedoraproject.org/wiki/Talking_points_SOP, add it to the the
table on the F13 page with supporting information. Please make your
contributions and changes on the wiki page, so that the Marketing team
can efficiently capture and consider your input.
The Marketing team will make final adjustments to the list of talking
points at their meeting on February 23, which will be announced on the
marketing list and is open to everyone. If you are interested in
attending the meeting, the agenda, location, and time details can be
found at http://fedoraproject.org/wiki/Marketing_meetings. Following
the meeting, the finalized list of talking points will be announced,
and posted to https://fedoraproject.org/wiki/Fedora_13_Talking_Points.
We welcome you to participate in the process!
Cheers,
-Robyn
13 years, 3 months
Fedora 13 has been branched!!
by Jesse Keating
That's right folks, we are now branched for Fedora 13. What does this
mean to you? Well that depends on who "you" are, here are some "you"s
that we wrote about:
https://fedoraproject.org/wiki/No_frozen_rawhide_announce_plan#Use_Cases
The real take away here is explained at
https://fedoraproject.org/wiki/Branch_Freeze_Policy
The upshot is that if you want to get a build into Fedora 13, you gotta
build from F-13/ and you gotta put it in bodhi. The good news is that
if your package isn't critical path, it's just like any other update in
bodhi, you decide when it goes stable. If it's critical path, releng or
QA will have to give it karma, but that means somebody will look at it!
(We're working on ways to make it more visible to the user that your
package is critical path).
There are new paths on the mirrors too:
pub/fedora/linux/development/rawhide <-- this is the new home of
rawhide. Builds from devel/ go here. This is now the F-14 development
ground.
pub/fedora/linux/development/13 <-- this is the branched Fedora 13.
Builds from F-13/ that make it through bodhi as stable show up here.
This is what we'll use to make the Alpha, Beta, Final release and all
the snapshots in between and the nightly attempt at instllable images.
pub/fedora/linux/updates/testing/13 <-- this is where the testing
updates go for the branched 13. Test 'em here before they go to stable.
For a better picture, see
https://fedoraproject.org/wiki/No_frozen_rawhide_announce_plan#Tree.2FRep...
I have disabled the rsync part of the rawhide compose process so that I
can do things by hand tomorrow and ensure we don't screw up the mirrors,
so you'll see a delay in things. We'll also do the branched tree
compose by hand as well and then sync the output at the same time to
preserve hardlinks. It'll be a fun day! Hop by #fedora-devel if you've
got questions and somebody will try to help you.
Welcome to the world of No Frozen Rawhide!!!
--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
13 years, 3 months
CVS Outage Notification - 2010-02-17 00:00 UTC
by Jesse Keating
There will be a CVS outage starting at 2010-02-17 00:00 UTC, which will
last approximately 3 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2010-02-17 00:00 UTC'
Affected Services:
CVS / Source Control
Unaffected Services:
Everything else.
Reason for Outage:
The CVS server will not accept connections so that we can mass-branch for Fedora 13.
Contact Information:
Please join #fedora-admin in irc.freenode.net or respond to this email to track
the status of this outage.
--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
13 years, 3 months