Alpha refresh
by Jesse Keating
Last night I created a new tag, f11-alpha-2, and refreshed it with
today's rawhide content. This is our new alpha tag, the one which we'll
be re-verifying our test results and using for the Alpha.
Unfortunately things in yum land broke a bit last night, and I had to
add createrepo and yum builds on top of what we tagged last night, so
today's rawhide isn't so... good. I'll be doing a mash in PHX of the
new alpha tag and it'll be somewhat available for people to sync up
against.
From this point on, tagging should only be for critical items.
--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
15 years, 3 months
#1245: Need btrfs-progs-0.18-3 tagged for f11a
by Fedora Release Engineering
#1245: Need btrfs-progs-0.18-3 tagged for f11a
-----------------------------+----------------------------------------------
Reporter: josef | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: Fedora 11 Alpha | Component: cvs
Keywords: |
-----------------------------+----------------------------------------------
Hello,
Sorry about this, but apparently installing to btrfs does not work
properly because btrfs's mkfs does not allow you to do label's with /'s in
it. I've fixed this and built a new package, btrfs-progs-0.18-3, to allow
this to work. Can this be tagged for f11a, since installing to btrfs
without this patch will not work at all. Thanks,
Josef
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/1245>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
15 years, 3 months
#1254: Include net6 and obby in updates buildroot
by Fedora Release Engineering
#1254: Include net6 and obby in updates buildroot
---------------------+------------------------------------------------------
Reporter: lmacken | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
---------------------+------------------------------------------------------
net6-1.3.9-1 and obby-0.4.7-1 are needed in the buildroot to build the
latest gobby.
The following builds need to be included::
net6-1.3.9-1.fc10
net6-1.3.9-1.fc9
obby-0.4.7-1.fc10
obby-0.4.7-1.fc9
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/1254>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
15 years, 3 months
#1246: Please push mono-2.2-1.fc10 onto the buildroot
by Fedora Release Engineering
#1246: Please push mono-2.2-1.fc10 onto the buildroot
-----------------------------------------+----------------------------------
Reporter: paul(a)all-the-johnsons.co.uk | Owner: rel-eng(a)lists.fedoraproject.org
Type: enhancement | Status: new
Milestone: | Component: koji
Keywords: |
-----------------------------------------+----------------------------------
Hi,
I need to be able to build the full mono stack for pushing into f10.
Currently, I am unable to do the build as everything gets built against
the version currently in updates-testing (2.2-1). It would not be a good
idea to move this into updates as a lot of other apps would break.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/1246>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
15 years, 3 months
Alpha Release Readiness
by John Poelstra
With the Alpha Release for Fedora 11 scheduled for Tuesday, February 3,
2009, this means it is time to meet again with representatives from each
of the teams to have our release readiness meeting. We usually have
this meeting at 18:00 UTC (13:00 EST) the Wednesday before, which means
next Wednesday, January 28, 2009, is the day.
On Monday, January 26, 2009, I will be sending out the dial-in
information and a meeting reminder to all the attendees.
In the meantime I need to know who will be representing your group at
these meetings for the Fedora 11 meetings. Usually this is the
designated team leader, but I wanted to ask to make sure you coordinate
within your team to make sure someone comes. When responding to this
list, please CC me so that I am sure to see the reply.
This message is going out to the respective mailings lists for these groups:
Ambassadors
Artwork/Design
Documentation
FESCo
Infrastructure
Marketing
Quality
Release Engineering
Translation
Websites
Thanks,
John
15 years, 3 months