#3419: Remove geronimo-specs from F14/rawhide
by Fedora Release Engineering
#3419: Remove geronimo-specs from F14/rawhide
----------------------+-----------------------------------------------------
Reporter: jjohnstn | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
----------------------+-----------------------------------------------------
The package geronimo-specs should be removed from F14/rawhide. It is
being replaced by geronimo-jta and geronimo-jms packages.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3419>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
14 years, 3 months
#3417: Please block smashteroid from F-13 and rawhide
by Fedora Release Engineering
#3417: Please block smashteroid from F-13 and rawhide
------------------------+---------------------------------------------------
Reporter: jwrdegoede | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
------------------------+---------------------------------------------------
Hi,
I've gotten a mail from upstream that they have been contacted by
Intellivision that
smashteroid looks too much like Astrosmash. So upstream has ceased
distributing
smashteroid and asked us to do the saem.
Thus please block smashteroid from F-13 and rawhide, I'll mark it as a
dead.package
and retire it in pkgdb.
Thanks,
Hans
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3417>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
14 years, 3 months
#3418: I need a buildroot override for gnome-desktop-2.28.2-5.fc12
by Fedora Release Engineering
#3418: I need a buildroot override for gnome-desktop-2.28.2-5.fc12
---------------------+------------------------------------------------------
Reporter: mclasen | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
---------------------+------------------------------------------------------
I need to build control-center and nautilus against this version so that I
can ship them all three together in one update.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3418>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
14 years, 3 months
Re: Spins late TM approval
by Jeroen van Meeuwen
On 02/18/2010 04:09 PM, Adam Miller wrote:
> On Thu, Feb 18, 2010 at 4:32 AM, Jeroen van Meeuwen <kanarip(a)kanarip.com> wrote:
> <snip>
>>
>> The list of spins at this moment in time is at:
>>
>> https://fedoraproject.org/wiki/Category:Spins_Fedora_13
>>
>> 9 of these are to be included in the Release, excluding Desktop and KDE
>> which for some reason are outside of the Spins SIG's processes completely.
> <snip>
>
> Why exactly are these two excluded from the spins process?
>
I can't think of any reason.
-- Jeroen
14 years, 3 months
Re: Spins late TM approval
by Jesse Keating
On Thu, 2010-02-18 at 09:09 -0600, Adam Miller wrote:
> Why exactly are these two excluded from the spins process?
Because they have been granted permanent spin status by the board.
--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
14 years, 3 months
Bodhi NFR stable mash bug
by Josh Boyer
I think I figured out why bodhi is trying to mash f13-updates (maybe).
There seems to be a bug in the repo detection when we resume. The
code looks like:
for update in self.updates:
release = update.release
# [No Frozen Rawhide] Don't mash stable repos for pending releases
if update.request == 'stable' and release.locked:
continue
if self.resume:
self.repos.add(release.stable_repo)
self.repos.add(release.testing_repo)
elif update.request == 'stable':
self.repos.add(release.stable_repo)
<snip>
So I think what happened is that on the first push attempt it
correctly skipped f13-updates. However, since the bodhi configs
were all horked due to permissions, we had to resume the push.
The above code seems to skip f13-updates initially, but then
blindly add it in the resume case (I think).
I'm not sure we actually want to mash f13-updates right now. I
could create the f13-updates.mash file really easily, but that
seems like the incorrect action to do.
If bodhi is fixed for this bug, we could roll out a new one and
then resume the push again. I don't really know of another
solution to our current problem.
josh
14 years, 3 months
No Frozen Rawhide help
by Paul W. Frields
Hi Docs team,
The release engineering team needs our help with some wiki revamping.
Specifically Rawhide, our development branch for software packages,
has changed in the Fedora 13 cycle, pursuant to what we call the "No
Frozen Rawhide" (NFR) proposal.
In the past, changes in Rawhide would slow as we got into the testing
(Alpha, Beta) phases for a release. In theory, fewer changes would be
allowed in the closer we get to release, and those allowed in would be
subject to more scrutiny, to stabilize the release. As a result,
right after the release is composed and tested successfully, Rawhide
would be unblocked like a dam, and the resulting flood of changes
would typically result in an unusable Rawhide for some time while
people pick up the wreckage and fix things.
Pursuant to NFR, we've just branched for Fedora 13 early, and
separated that branch from Rawhide. Rawhide is now carrying those
packages that will be in Fedora 14, about 9 months from now. As a
result, we can apply a higher level of scrutiny to the Fedora 13
branch, while Rawhide will continue to roll on, only hopefully without
a point of massive breakage.
A team of people gathered last Friday to put together explanations of
how this scheme works, and how it affects people in various
categories, including packagers, testers, mirror admins, and others:
https://fedoraproject.org/wiki/No_frozen_rawhide_announce_plan
What we need now is for a few people to help with fixing wiki pages,
most of which have been listed here on that page:
https://fedoraproject.org/wiki/No_frozen_rawhide_announce_plan#Existing_D...
You don't need to be an experienced Rawhide user or tester to
understand the information on this page. But if there are any
questions, everyone on the crew who participated in the NFR conference
last week is available on IRC to answer questions.
What do you need to do?
* Show up on IRC Freenode at #fedora-docs -- instructions for doing
that are here: https://fedoraproject.org/wiki/How_to_use_IRC
* Ping me, "stickster," and tell me you want to help. I'll get you
started on a specific page.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
Where open source multiplies: http://opensource.com
14 years, 3 months
