[releng] Issue #8031: Need +1: policy change re. module default stream
changes & Fedora Changes
by Adam Samalik
asamalik reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
The Modularity WG is changing the policy regarding module default stream changes & Fedora Changes. It is a minor policy change that doesn't require any changes in code. I'd like to get a formal +1 from RelEng and FESCo on the change before publishing it.
The summary would be: "Instead of rigidly requiring a Fedora Change for all module default stream changes, we are relaxing the policy to 'submitting a Fedora Change based on packager's best judgement'. We are also restricting changes to major Fedora releases. This makes it more consistent with how we handle major changes in traditional packages."
For more details, please see the current policy [1] (please note it's described quite "efficiently"), the new policy approved by the Modularity WG [2], and optionally a set of scenarios covering module default stream changes [3].
[1] https://docs.fedoraproject.org/en-US/modularity/making-modules/managing-d...
[2] https://tree.taiga.io/project/modularity-wg/us/77
[3] https://pagure.io/modularity/working-documents/blob/master/f/lifecycles-u...
* When do you need this? (YYYY/MM/DD)
No date.
* When is this no longer needed or useful? (YYYY/MM/DD)
No date.
* If we cannot complete your request, what is the impact?
Packagers would continue to be required to submit a Fedora change for every module default stream change, even in cases one wouldn't be submitted in a similar change introduced by traditional packages — making the workflows between the two delivery methods (trad packages & modules) inconsistent.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8031
5 years, 3 months
eInvoice Notification - 17 January 2019
by Ben Cotton
Dear Customer,
Attached is the last invoice.
Thanks in anticipation.
Ben Cotton
bcotton(a)redhat.com
If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender.
5 years, 3 months
RelEng schedule tasks
by Ben Cotton
I am beginning to prepare the schedule for Fedora 31. One thing I want
to do is to make sure it still accurately reflects the work of
different teams within Fedora. Please look at the tasks on your team's
schedule [1] and discuss them in your team. Let me know if there are
tasks that should be added, removed, or modified. You can email me
directly or file an issue in Pagure[2].
I ask that you please provide feedback by Friday, 18 January, although
I will be able to incorporate changes after that.
[1] https://fedorapeople.org/groups/schedule/f-30/f-30-releng-tasks.html
[2] https://pagure.io/fedora-project-schedule/issues
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
5 years, 3 months
[release] pungi 4.1.32
by Lubomír Sedlář
Hello everyone,
a new version of Pungi is available! The 4.1.32 build is ready to be
used. There are updates waiting in Bodhi to go to updates-testing.
Ideally you should use the 4.1.32-3.fcX build.
This is a minor bug-fix release.
The old pungi command has been updated to use createrepo_c for creating
repos and productmd for generating metadata.
There have been a few tweaks and improvements to documentation.
It is now possible to configure rootfs size for lorax for traditionall
installer, not just the one based on ostree.
Refer to the documentation [0] for details on what configuration
options are available.
[0] https://docs.pagure.org/pungi/index.html
If you encounter problems or need general help, stop by #fedora-releng
IRC channel or file issues in Pagure.
Happy composing!
Lubomír
5 years, 3 months