#1107: auto-cleanup rawhide trees
-------------------------+--------------------------------------------------
Reporter: notting | Owner: rel-eng(a)lists.fedoraproject.org
Type: enhancement | Status: new
Milestone: | Component: koji
Keywords: |
-------------------------+--------------------------------------------------
Rawhide tree expiry is manual at the moment, unless I missed something.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/1107>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4985: Extend test image creation SOP to require notification of delays
----------------------+-----------------------------------------------------
Reporter: adamwill | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: koji
Keywords: |
----------------------+-----------------------------------------------------
Working through the F16 QA retrospective here:
https://fedoraproject.org/wiki/Fedora_16_QA_Retrospective
One of the notes is:
"jlaska - Alpha TC1 - Missed the Alpha-TC1 milestone by 1 week, little to
no communication regarding status. With only two weeks Alpha ISO test
time, losing 50% of time almost certainly results in a slip. See rel-eng
ticket#4844 . None of the Alpha rel-eng release tickets have been filed at
this time.
adamw - perhaps releng image compose SOP should require updating of ticket
with progress info, especially when image compose / delivery is delayed?"
So: this ticket proposes that the releng 'Composing test images' SOP -
https://fedoraproject.org/wiki/Composing_test_images - should be extended
to require whoever is creating the images to post a comment on the image
request ticket if the compose is delayed, explaining the reasons for the
delay (so that any other interested party can attempt to contribute to
resolving them) and giving a best estimate of an ETA if possible (so other
groups can adjust their scheduling as best they can).
Thanks!
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4985>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4071: Block pushes to origin/ in gitolite ACLs
----------------------+-----------------------------------------------------
Reporter: jkeating | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: git
Keywords: |
----------------------+-----------------------------------------------------
Common typo to create a new branch that starts with "origin/". We can
stop that at the ACL level.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4071>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4355: metadata for "grouped" files on master mirror
---------------------+------------------------------------------------------
Reporter: mdomsch | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: other
Keywords: |
---------------------+------------------------------------------------------
This may be less of an issue now that we don't have the split CD set, but
I would like it if rel-eng could produce a file into the master mirror
tree for "groups" of files that should be a single consistent download
set, such as a DVD and the checksum file, or the set of files that are
together inside a single torrent. MirrorManager is growing the idea of a
"file group", a single requestable entity that will return a metalink
listing each of the files in the file group. The intent was to use it for
the multi-CD download sets, but it's just as valuable for the DVD and
checksum file, or other similar groups. But it needs to be a file (say,
.fileset or something), in a directory that MM can find and use to build
the FileGroups.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4355>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#3903: change component owner in bugzilla
----------------------+-----------------------------------------------------
Reporter: mmaslano | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: other
Keywords: |
----------------------+-----------------------------------------------------
Could you create perl-fedora-maint as bug owner for all my perl-* modules
and perl component? I'm sharing bugs with my colleagues in RHEL and we'd
like to have it also for Fedora. I suppose set up mailing list is also
needed.
This should be applied only for perl modules, where I am an owner of the
package. Not only co-maintainer.
The group perl-fedora-maint should include mmaslano, ppisar, psabata.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3903>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#3624: fullfilelist changes
-------------------------+--------------------------------------------------
Reporter: mmcgrath | Owner: rel-eng(a)lists.fedoraproject.org
Type: enhancement | Status: new
Milestone: | Component: other
Keywords: |
-------------------------+--------------------------------------------------
After each push, we need to run the following command:
rsync -r . > fullfilelist
This should overwrite the fullfilelist that's there and isn't very useful
at the moment:
http://download.fedora.redhat.com/pub/fedora/fullfilelist
We can't do this via a cron job, it has to go out after each push so it
needs to be added to those scripts.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3624>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#3761: add gpg signature for .treeinfo file and/or add CHECKSUM file for unsigned
content of images
----------------------+-----------------------------------------------------
Reporter: jkeating | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: other
Keywords: meeting |
----------------------+-----------------------------------------------------
Description of problem:
Currently the only way to verify the contents of .treeinfo or the
installer
images is to download the .iso and the regarding -CHECKSUM file and check
it.
But e.g. preupgrade does not download the .iso but the *.img files, the
kernel
and the .treeinfo directly from a mirror. Therefore it is also not
possible to
easily verify these files. I guess the preupgrade way of updating is
somehow
popular, therefore it should be possible to do this securely.
I filed a bug against preupgrade for not verifying anything and not
announcing
this here: bug 509338
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3761>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4267: collectd in EPEL
----------------------+-----------------------------------------------------
Reporter: mmcgrath | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: mash
Keywords: |
----------------------+-----------------------------------------------------
Can we get collectd in EPEL set to disable multi-lib? It has become an
issue on EPEL where installing "collectd" via yum creates conflicts it
shouldn't.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4267>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#4324: Change product string in pungi for better syslinux usability
-------------------+--------------------------------------------------------
Reporter: duffy | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: other
Keywords: |
-------------------+--------------------------------------------------------
Right now when you boot Fedora live media or otherwise call up Syslinux,
you are greeted with:
"Welcome to Fedora-14-x86_64-Live-Desktop!"
It's not the most welcoming message though because the string is a bit
unwieldy and hard-to-read. Syslinux pulls from the PRODUCT string produced
via pungi:
scripts/mk-images.x86: sed -i "s/@PRODUCT@/$PRODUCT/g"
$MBD_BOOTTREE/syslinux.cfg
I was hoping that string produced by pungi could be cleaned up a bit to be
more friendly. Some examples I think that would be better:
Fedora 14 (32-bit)
Fedora 14 (64-bit)
Fedora 14 (32-bit DVD)
Fedora 14 (64-bit DVD)
Fedora 14: KDE Plasma (32-bit)
Fedora 14: KDE Plasma (64-bit)
Fedora 14: LXDE (32-bit)
Fedora 14: LXDE (64-bit)
Fedora 14: Xfce (32-bit)
Fedora 14: Xfce (64-bit)
Fedora 14: Electronic Lab (32-bit)
Fedora 14: Electronic Lab (64-bit)
Fedora 14: Design Suite (32-bit)
Fedora 14: Design Suite (64-bit)
Fedora 14: Sugar on a Stick (32-bit)
Fedora 14: Sugar on a Stick (64-bit)
Fedora 14: Games Spin (32-bit)
Fedora 14: Games Spin (64-bit)
Fedora 14: Security Lab (32-bit)
Fedora 14: Security Lab (64-bit)
So the rules I'm suggesting for the strings:
- The default desktop is called simply "Fedora $VERSION ($ARCH)"
- Any non-default spins are called "Fedora $VERSION: $NAME_OF_SPIN
($ARCH)"
- The spin name is derived from either the http://fedoraproject.org/en
/get-fedora-options#desktops get.fpo options page or the
spins.fedoraproject.org full name for the spin. (KDE is probably updating
theirs to KDE Plasma as reflected in example strings above.)
- Put the arch in () after the name of the spin. Where arch is '32-bit',
'64-bit', 'Power PC', etc. The arch names here are suggested to be
consistent with what the downloads are labeled on our main web pages
(get.fpo and spins.fpo)
- If it's live media, don't indicate that, don't point it out. Only
indicate if it's a DVD.
If it's DVD, point it out after the arch in the ( )
- $VERSION should be a whole number without decimals for a final release.
For test releases / release candidates it would be nice to indicate
something like, '14.92 RC1' '14.91 Nightly 06 Jan 2011' but that's up to
your discretion!
This is where the text will appear in syslinux:
https://fedoraproject.org/w/uploads/3/3d/Installux-syslinux-
prop1-proto1-ss2.png
What do you think?
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4324>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project