[releng] add some variables for QA to run-pungi add some comments on the purposes of them all
by Dennis Gilmore
commit 469ffb74d1dddea864d5fb9d99a537d6b210cce1
Author: Dennis Gilmore <dennis(a)ausil.us>
Date: Fri Mar 20 14:42:13 2015 -0500
add some variables for QA to run-pungi add some comments on the purposes of them all
scripts/run-pungi | 13 +++++++++++++
1 files changed, 13 insertions(+), 0 deletions(-)
---
diff --git a/scripts/run-pungi b/scripts/run-pungi
index 01b9b47..c1bed98 100755
--- a/scripts/run-pungi
+++ b/scripts/run-pungi
@@ -14,11 +14,24 @@ KICKSTARTS=/srv/pungi/spin-kickstarts/
ATOMIC=/srv/pungi/fedora-atomic/
ATOMICDEST=/srv/pungi/atomic/
+# SHORTCOMPOSE: a short reference to the compmose it is 1 for RC1 and TC1 for TC1
+# BUILD: added for QA to refer to the compose by RC1 or TC1
+# MILESTONE: is for QA refers to Alpha/Beta/Final
+# SHORTVERSION: is a shortened version of the Version passed in drops off _TCX
+# COMPOSE: is passed in for RC's only in the format of _RCX
+
SHORTCOMPOSE=$(echo $COMPOSE|sed -e 's|_RC||g')
+BUILD=$(echo $COMPOSE|sed -e 's|_||g')
+MILESTONE=$(echo $VERSION|sed -e 's|_T.*||' -e 's|.*_||')
SHORTVERSION=$VERSION
[ -z "$COMPOSE" ] && {
SHORTVERSION=$(echo $VERSION|sed -e 's|_T.*||')
SHORTCOMPOSE=$(echo $VERSION|sed -e 's|.*_||g')
+ BUILD=$(echo $VERSION|sed -e 's|.*_||g')
+}
+
+[ -z "$MILESTONE" ] && {
+ MILESTONE=Final
}
FULLPATH=$(pwd)
9 years, 1 month
#6137: 1 package missing from mirrors
by Fedora Release Engineering
#6137: 1 package missing from mirrors
----------------------------+-------------------
Reporter: limb | Owner: limb
Type: task | Status: new
Milestone: Fedora 22 Beta | Component: koji
Keywords: | Blocked By:
Blocking: |
----------------------------+-------------------
pcmanfm-qt-0.9.0-7.fc21 is missing, possible simultaneous push with
pcmanfm-qt-0.9.0-5.fc21.
Retagged.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6137>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
9 years, 1 month
#6138: Avoid having TC tree lost when going gold
by Fedora Release Engineering
#6138: Avoid having TC tree lost when going gold
----------------------------+------------------------
Reporter: walters | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 22 Beta | Component: koji
Keywords: | Blocked By:
Blocking: |
----------------------------+------------------------
For Fedora 21, the OSTree repository commit was discarded and a new tree
created. This means that the original commit used for the cloud image is
lost.
This isn't a very serious problem, but it'd be good to avoid for F22.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6138>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
9 years, 1 month
#6127: Improve package removal in EPEL
by Fedora Release Engineering
#6127: Improve package removal in EPEL
----------------------------+------------------------
Reporter: pnemade | Owner: rel-eng@…
Type: enhancement | Status: new
Milestone: Fedora 22 Beta | Component: epel
Keywords: | Blocked By:
Blocking: |
----------------------------+------------------------
Currently What I understood, email comes on epel-devel list which says
like "Orphaned Packages in epel5 (2015-03-14)" and then followed by actual
package removal. This is not giving a sufficient time for people to read
such generic email.
I suggest email personally to people which get affected by such package
removals. e.g. when time comes to remove orphaned packages, pick such
packages one by one, generate report what other owned packages also be
removed. Email such owned packages people that their package will be
picked for removal in next 3-7 days. Leave the further decision to those
people. They can either find someone to own dependent orphaned package or
own it themselves.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6127>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
9 years, 1 month
Pkgdb2 1.24
by Pierre-Yves Chibon
Hi everyone,
The next pkgdb2 release (1.24) will be a pretty big releases, to give you an
idea this is its current changelog:
- Allow package admins to retire a package
- Anitya integration on the package's detail page
- Fix orphaning package having a group as PoC
- Add the possibility to request action from the pkgdb admins and releng.
These actions include:
- Request a new package to be added to pkgdb (after completed its review on
bugzilla)
- Request a new branch for an existing package
- When requesting a new branch, current package admins have 1 week to agree
or disagree with the request
- If they disagree the request is blocked (they have to specify a reason)
- After a week, or earlier if they agree, the request is passed onto the
pkgdb admins and releng for processing.
These new actions can be processed via pkgdb-admin which is shipped as part of
packagedb-cli (ie next to pkgdb-cli).
Since these changes might be pretty big and impact multiple person, I would like
to hear when people think it would be best to make the release.
Note: I will not do it today, but basically I could from tomorrow :)
Note2: As it will likely take a little time for people to get adjusted to the
new workflow (that needs to be documented & so on), there will likely be a time
for pkgdb admins and releng when they will have to check both bugzilla and
pkgdb.
Note3: As I would not be surprised that we run into some bugs and since freeze
is not that far either, the earlier the better :)
Thanks,
Pierre
PS: Also sent to the rel-eng list but please let's keep this on the infra list
9 years, 1 month
