rel-eng October 2014

rel-eng@lists.fedoraproject.org

16 participants
143 discussions

#6023: allow Peter Robinson to restart sigul bridges
by Fedora Release Engineering 09 Feb '15

09 Feb '15

#6023: allow Peter Robinson to restart sigul bridges -----------------------------+------------------------ Reporter: till | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Final | Component: koji Keywords: meeting | Blocked By: Blocking: | -----------------------------+------------------------ The sigul bridges are very unstable, but currently nobody from Europe can restart it, therefore it might be unusable for a long time until Dennis Gilmore or Kevin Fenzi find the time to restart it. Especially to get the autosigner run smoothly it would be better to have at least one more being able to restart the bridges. Peter Robinson would be a good candidate. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6023> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 5

#5654: Report full image creation for quality website updates
by Fedora Release Engineering 19 Jan '15

19 Jan '15

#5654: Report full image creation for quality website updates -----------------------------+------------------------ Reporter: shaiton | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 19 Final | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Hi, we already discussed a bit about this issues with nirik, before the F19 release day. However, yesterday was worse as expected. Please see the number of fixes: https://git.fedorahosted.org/cgit/fedora-web.git/log/ (7 important fixes after the merge into prod aedf487eb). == Summary of major issues: * http://torrent.fedoraproject.org/spins/ changed to http://torrent.fedoraproject.org/torrents and we had no idea about this. * The naming scheme of the file changed which introduced a bug in our spins website build as it is based against the Json file. We had to fix a 2 years old python code. And we did not know about this. * Each release we have the 32 bit arch named i686 or i386, it's always changing. We defined variables in order to help us maintain the websites.. And this does not help us. I know that it depends of the proc instruction set. But where is the need to change that really? Could we avoid it? Sooner or later we will drop 32 bit arch... Couldn't we define which arch to stick with? * We don't know before last minute if the Spin has built for GA and therefore if it is going to be released. We need to check it manually. And really, we can't do it all manually. (as lazy programmers we can't even think about this). * Even the spins name has changed in the past, which break our code and already existing URLs. And then we need to define URL redirect... I hope jam-kde won't be changed to jam-mate-compiz-fusion-dark at some point.. Just wondering... * The secondary (ARM) path changed from Images/arm/ to Images/armhfp/.. I understand the need to tell if it's using FP or not, but again we didn't know about this before testing in prod. That should not happen again. Please, help me define the best way to avoid this. It could be improving SOP, or updating a file after each build.. whatever. It's a probably wider collaboration issues as it is involving primary, secondary, SIGs (spins, cloud).. But starting with Releng we can probably sort this and define the smoother solution for all. What we need in a simple way (script friendly) and easy to generate for you is a way to get: All image full name, path (if possible before release), size (not needed for torrents), format (torrent, spin, dvd, cloud... whatever) and checksum. What can't be available easily can have an easy process to get them or at least we need to know how and when to get them. The most important of course is the image full name. If we don't know that this image exists (or died), we won't be able to update it. Any brillant idea? -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5654> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 9

#5978: Please create a f21-gnome side tag
by Fedora Release Engineering 19 Jan '15

19 Jan '15

#5978: Please create a f21-gnome side tag -----------------------------+------------------------ Reporter: kalev | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 21 Alpha | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Hi, Please create a new f21-gnome side tag and build target. We'll be building GNOME 3.13.91 early next week and this would help ensure it doesn't cause instabilities in F21 proper while we're preparing it. Thanks, Kalev -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5978> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 8

#5922: skip 32-bit arches for fedora-cloud-atomic.ks and fedora-cloud-bigdata.ks
by Fedora Release Engineering 19 Jan '15

19 Jan '15

#5922: skip 32-bit arches for fedora-cloud-atomic.ks and fedora-cloud-bigdata.ks -----------------------------+------------------------ Reporter: mattdm | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Final | Component: other Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ The Cloud SIG decided that the Atomic and Big Data images will be 64-bit only. (Docker currently only works in 64 bits, and while big data tools might work, the target audience is almost always on 64 bits). -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5922> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 4

#5859: Releng improvements ideas 2014
by Fedora Release Engineering 19 Jan '15

19 Jan '15

#5859: Releng improvements ideas 2014 -----------------------------+------------------------ Reporter: till | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Final | Component: other Keywords: meeting | Blocked By: Blocking: | -----------------------------+------------------------ Ideas to improve releng: - Properly announce in advance if meetings are skipped -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5859> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 5

#5891: Deliverables and release engineering changes for Fedora.Next/Fedora 21
by Fedora Release Engineering 19 Jan '15

19 Jan '15

#5891: Deliverables and release engineering changes for Fedora.Next/Fedora 21 -----------------------------+------------------------ Reporter: jreznik | Owner: rel-eng@… Type: enhancement | Status: new Milestone: Fedora 21 Alpha | Component: other Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Fedora Working Groups are discussing different options how to deliver specific Fedora Products. These deliverables has to be collected (and agreed on) to plan changes in Fedora release engineering process. This ticket should serve to collect requirements from WGs in a centralized way (as there's possible overlap etc). For specific implementation details, new tickets will be created. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5891> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 7

#5944: drop "bigdata" from build-cloud-images for f21 -- feature was postponed
by Fedora Release Engineering 19 Jan '15

19 Jan '15

#5944: drop "bigdata" from build-cloud-images for f21 -- feature was postponed -----------------------------+------------------------ Reporter: mattdm | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Final | Component: other Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Big Data cloud image isn't going to make the milestone, so we should stop trying to make the image. Still hoping to do this for F22, so if we can keep the rawhide one, awesome. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5944> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 2

#6004: Trigger new Atomic builds based on bash vulnerability
by Fedora Release Engineering 19 Jan '15

19 Jan '15

#6004: Trigger new Atomic builds based on bash vulnerability -----------------------------+------------------------ Reporter: jzb | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 21 Alpha | Component: koji Keywords: security | Blocked By: Blocking: | -----------------------------+------------------------ We have packages out for the bash vulnerability for Fedora 21 alpha, but users cannot "yum update" the Atomic images. We need to spin + push out new images and/or an update tree for users who are on Atomic. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6004> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 1

#5988: F21 stable push requests
by Fedora Release Engineering 05 Dec '14

05 Dec '14

#5988: F21 stable push requests -----------------------------+------------------------ Reporter: adamwill | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 21 Final | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ This ticket will be used for requesting pushes of tested blocker / freeze exception fixes during F21 release freezes. See https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process and https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process. Similar to TC/RC request tickets, this ticket can be closed by releng after each push and re-opened by QA each time a new push is needed. First request, current Alpha blocker / FE fixes with sufficient karma to be pushed: * [https://admin.fedoraproject.org/updates/FEDORA-2014-10184 selinux- policy-3.13.1-78.fc21] for [https://bugzilla.redhat.com/show_bug.cgi?id=1112387 #1112387] * [https://admin.fedoraproject.org/updates/FEDORA-2014-10210 GNOME 3.13.91 mega-update] for [https://bugzilla.redhat.com/show_bug.cgi?id=1135890 #1135890], [https://bugzilla.redhat.com/show_bug.cgi?id=1136959 #1136959] and [https://bugzilla.redhat.com/show_bug.cgi?id=1136953 #1136953] * [https://admin.fedoraproject.org/updates/xorg-x11-drv- intel-2.99.914-3.fc21] for [https://bugzilla.redhat.com/show_bug.cgi?id=1133142 #1133142] -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5988> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 37

[PATCH] Remove requirement on system-release-product
by Stephen Gallagher 18 Nov '14

18 Nov '14

This was added to be overcautious (to ensure that every installation of Fedora has at least one of the fedora-release-* packages installed). However, this was both redundant (all install media includes at least one) and problematic. Since some of the fedora-release-$PRODUCT packages have additional explicit deps, it was causing a circular dependency loop in certain situations. See https://bugzilla.redhat.com/show_bug.cgi?id=1156198 for additional details.

2 1

← Newer
1
2
3
4
5
6
7
8
...
15
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng October 2014