November 2009 - rel-eng - Fedora Mailing-Lists

#3158: Buildroot override requests: toot2 and others

by Fedora Release Engineering

#3158: Buildroot override requests: toot2 and others ------------------+--------------------------------------------------------- Reporter: oget | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: koji Keywords: | ------------------+--------------------------------------------------------- Hi. I need to have [http://koji.fedoraproject.org/koji/taskinfo?taskID=1807357 toot2-3-0.6.227svn.fc11] [http://koji.fedoraproject.org/koji/taskinfo?taskID=1807352 toot2-3-0.6.227svn.fc12] in the buildroot so I can build tootaudioservers. After that I will need to have tootaudioservers tagged to build frinika. Thanks! -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3158> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

14 years, 5 months

1
2
0 / 0

Meeting (Fedora talk?) to discuss no frozen rawhide

by Jesse Keating

Now that 12 is in the can, we need to start talking about 13, and how no frozen rawhide comes into play. I'd like to set aside some time Wed or later to have a Fedora talk + gobby call where we can review the proposal, see where we are with it, and walk through the Fedora 13 development cycle in light of the proposal, so that we can outline where work needs to be done and deadlines for that work. I currently have no meetings scheduled for Wed the 18th, so I'm available from 1700 UTC to 2300 UTC. -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating

14 years, 5 months

3
2
0 / 0

#3100: Tag request ghc-X11-1.4.6.1-1.fc11 for dist-f11-override

by Fedora Release Engineering

#3100: Tag request ghc-X11-1.4.6.1-1.fc11 for dist-f11-override ----------------------+----------------------------------------------------- Reporter: petersen | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Component: koji | ----------------------+----------------------------------------------------- {{{ Needed to build the new version of xmonad -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3100> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

14 years, 5 months

1
3
0 / 0

#2740: Please block gnupg package from dist-f13 it is retired

by Fedora Release Engineering

#2740: Please block gnupg package from dist-f13 it is retired -------------------+-------------------------------------------------------- Reporter: tmraz | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: koji Keywords: | -------------------+-------------------------------------------------------- Please block gnupg package from dist-f13 it is retired and obsoleted by gnupg2. The gnupg2 package in dist-f13 now contains all the necessary provides/obsoletes and also contains compat symlinks to the previously gnupg binaries so the scripts calling gpg/gpgv will keep working. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/2740> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

14 years, 5 months

2
2
0 / 0

#3156: override tag request for ipod-sharp-0.8.4-1.fc12

by Fedora Release Engineering

#3156: override tag request for ipod-sharp-0.8.4-1.fc12 ------------------+--------------------------------------------------------- Reporter: chkr | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: koji Keywords: | ------------------+--------------------------------------------------------- Please tag the following build into the buildroot for F12: https://koji.fedoraproject.org/koji/buildinfo?buildID=141273 The override is necessary to build banshee against it. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3156> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

14 years, 5 months

1
1
0 / 0

Fedora 13 Schedule Discussion Take II

by John Poelstra

I realize there hasn't been general consensus yet on what we want, but I took another stab at things trying to accommodate everyone as much as possible. I created two new scenarios to see if there are parts or wholes that resonate with people. Constructive feedback such as what to change and where the adjustment points should be is helpful. == SCENARIO I == --include Test Composes before freezes (desired by Jesse & James) --shrink Alpha testing period to 3 weeks (from 4) --I realize Bill prefers 2 here, but considering this is the first test release (not the second as in all the releases before Fedora 12), 2 weeks seems awfully short, plus it is just that much sooner that you have to create another public release. --by shrinking Alpha testing period by one week (now three weeks), add that time to development and feature creation duration at the front of the schedule. --hold beta testing period at three weeks o Fancy gantt chart pdf: http://poelstra.fedorapeople.org/schedules/f-13-draft/fedora-13-scenario1... o Boring html version: http://poelstra.fedorapeople.org/schedules/f-13-draft/f-13-scenario-1.html == SCENARIO II == --same as Scenario I with exception below --reduce beta testing period to two weeks and add extra week to development and feature creation duration at the front of the schedule. o Fancy gantt chart pdf: http://poelstra.fedorapeople.org/schedules/f-13-draft/fedora-13-scenario2... o Boring html version: http://poelstra.fedorapeople.org/schedules/f-13-draft/f-13-scenario-2.html == NOTE == I realize that the "alpha/beta testing periods" are unusual in the Fedora context with rawhide continuing to move and new testing content being made frequently. I also realize this potentially changes with the new rawhide proposal, but since it is not implemented yet I think it is too early to completely rely on it as the foundation of these schedules. I do think looking at the testing duration is helpful to bracket a period of time that these official test releases are available for wider consumption and testing and when releng has a break from creating images. Fedora 13 in the context of other releases http://poelstra.fedorapeople.org/schedules/f-13-draft/f8-f13-schedule-ana... == QUESTIONS == 1) James--how much time does QA believe we need for public testing of Alpha and Beta? 2) What other scenarios can I create to help us get to the final one? John

14 years, 5 months

1
0
0 / 0

#3154: Remove gstreamer-plugins-good-0.10.16-2.fc11 from F11-updates

by Fedora Release Engineering

#3154: Remove gstreamer-plugins-good-0.10.16-2.fc11 from F11-updates ---------------------+------------------------------------------------------ Reporter: mtasaka | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: koji Keywords: | ---------------------+------------------------------------------------------ [https://www.redhat.com/archives/fedora- list/2009-November/msg00905.html][[BR]] [https://admin.fedoraproject.org/updates/F11/FEDORA-2009-10937][[BR]] [https://admin.fedoraproject.org/updates/F11/FEDORA-2009-10647][[BR]] [[BR]] It seems that both updates requests of gstreamer-plugins-good was pushed into F11updates at the same time, and due to it koji shows the latest dist-f11-updates gstreamer-plugins-good is -2.fc11, not -4.fc11, which currently causes the conflict with gstreamer-plugins-base. [[BR]] [[BR]] Please remove gstreamer-plugins-good-0.10.16-2.fc11 from f11updates (and leave only -4.fc11).[[BR]] -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3154> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

14 years, 5 months

1
2
0 / 0

Fwd: F13 Schedule Proposal--please RESPOND

by John Poelstra

-------- Original Message -------- Subject: F13 Schedule Proposal--please RESPOND Date: Fri, 30 Oct 2009 10:28:42 -0700 From: John Poelstra <poelstra(a)redhat.com> To: rel-eng(a)fedoraproject.org I have had a Fedora 13 schedule drafted for several weeks based on the methodology we've established from previous releases. http://poelstra.fedorapeople.org/schedules/f-13/f-13-key-tasks.html I'm reluctant to publish this Fedora 13 draft because I think we can come up with something better. This thinking came out of a spreadsheet I built to calculate the actual number of days between the significant milestones in each of our schedules since Fedora 8 (see attached). Some of the comparisons between releases are surprising. Others lead me to believe we are making adjustments in the wrong places. One of the biggest issues this analysis shows is that because we insist on setting our next targeted release to Halloween or May Day we short change the next release when we slip the release under development. For example, Fedora 12 slipped by two weeks + one additional week added for conference attendance. This takes three weeks away from Fedora 13 and results in a 5.25 month release cycle. Questions: 1) Are we truly getting value out of the "Halloween/May Day" principle? 2) Desktop has said they could use more time to do polish, etc. How much longer would they propose? My question on fedora-desktop-list went unanswered. 3) With the advent of the test days and ISOs for those events, are we getting any value out of the weekly snapshots during Alpha? Should we keep doing them? My proposal: 1) Move to a solid 6 month release cycle--add 6 months to GA date of previous release with the exception that adjustments will be made when/if this collides with December holidays. I realize this could mess up synchronization with the Gnome schedule. 2) Eliminate weekly snapshots during Alpha since their value is questionable 3) Set the alpha and beta public testing durations to three weeks each. 4) Add new milestones for Desktop freezes, polish, and "work all done." Please get back to me by Wednesday, November 4, 2009. Thanks, John

14 years, 5 months

5
16
0 / 0

We can make fedora easier.

by Tareq Al Jurf

Hi all I think that we should change somethings in fedora that would make it easier. Things that whenever a new person starts fedora for the first time would change them. For example whenever i start fedora for the first time i change the behavior of the folders and make them open in browser can we make that default? Because i think most people do that. Regards -- Tareq Al Jurf Fedora Ambassador Riyadh, Saudi Arabia taljurf(a)fedoraproject.org

14 years, 5 months

2
1
0 / 0

#3153: Fixed: NFS *always* failing on reboots....

by Fedora Release Engineering

#3153: Fixed: NFS *always* failing on reboots.... -----------------------------+---------------------------------------------- Reporter: steved | Owner: rel-eng(a)lists.fedoraproject.org Type: defect | Status: new Milestone: Fedora 12 Final | Component: koji Keywords: | -----------------------------+---------------------------------------------- I just added a one liner to nfsd that will stop the NFS server from failing when configured to come up during boot... This could a bit embarrassing The bug reports are: https://bugzilla.redhat.com/show_bug.cgi?id=533893 https://bugzilla.redhat.com/show_bug.cgi?id=532270 (which has the one line patch) The Build: http://koji.fedoraproject.org/koji/taskinfo?taskID=1803998 Please consider for Final... -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3153> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

14 years, 5 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng November 2009