Re: F41 Change Deadlines and other important deadlines!

2024-06-20 Thread Petr Pisar 
V Thu, Jun 20, 2024 at 01:57:59PM +0100, Sérgio Basto napsal(a):
> I saw in key tasks:  "Mass Rebuild: RPMs first, then modules", modules
> aren't over ?

They are over. Fedora 38 was last one with modules. Though relengs keept the
modular repository empty over 2 releases to enable seamless upgrade. Fedora 41
should be again without the modular repository.

I opened  PR which
should fix it.

> BTW we continue to receive CVE's bugzilla reports on modules for
> nextcloud on epel 8 for example , how we stop that ? 
>
Close all module stream in PDC and then lock the components from Bugzilla.
As far as I know, the locking is done automatically for RPM packages, but
there is no automation for modules.

I opened a releng request .

-- Petr


signature.asc
Description: PGP signature
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: F41 Change Deadlines and other important deadlines!

2024-06-20 Thread Sérgio Basto 
Hello,

I saw in key tasks:  "Mass Rebuild: RPMs first, then modules", modules
aren't over ? 
BTW we continue to receive CVE's bugzilla reports on modules for
nextcloud on epel 8 for example , how we stop that ? 

Thank you


On Tue, 2024-06-18 at 09:46 +0100, Aoife Moloney wrote:
> Hi folks,
> 
> 
> A quick reminder that for the F41 development cycle[1], the system-
> wide changes submission deadline is today, June 18th. 
> This does not mean your change has to be accepted, it just means that
> you need to get your proposal filed by this date[2]. So if you are
> thinking of proposing a change, even if it's not fully fleshed out,
> consider submitting it anyway today and make use of our great
> community to iterate on your proposal in real time. 
> The self-contained change proposal deadline is July 16th
> 
> It's important to also note that the 'testable' deadline[3] for
> changes is August 6th, however please be mindful that this is also
> our branching date from Rawhide so it would be preferable to have
> your changes landed in rawhide and available for testing before this
> date. 
> 
> Your change, once approved to F41, landed in Rawhide for branching
> and testable, must then be 100% code complete[4] before we enter Beta
> Freeze on 20th August, or it will most likely need to be retargeted
> to F42.
> 
> Changes that are not code complete by the Beta Freeze date puts a big
> strain on the folks involved with each Fedora release, so by adhering
> to these dates, it helps the overall release process run much
> smoother, we all benefit from a higher quality release and a slightly
> less stressful crunch time at the end :) So thank you in advance for
> getting your changes ready in time for these milestones, it's hugely
> appreciated.
> 
> 
> Please dont hesitate to reach out with questions or if I can be of
> any help.
> 
> 
> Kindest regards,
> Aoife 
> 
> 
> [1] https://fedorapeople.org/groups/schedule/f-41/f-41-key-tasks.html
> [2]
> https://docs.fedoraproject.org/en-US/program_management/changes_policy/
> [3][4]
> https://docs.fedoraproject.org/en-US/program_management/changes_policy/#_change_process_milestones
> 
> 
> -- 
> 
>  
> Aoife Moloney 
>  
> Fedora Operations Architect
>  
> Fedora Project
> Matrix: @amoloney:fedora.im
> IRC: amoloney
> 
>  
> --
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue

-- 
Sérgio M. B.
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

F41 Change Deadlines and other important deadlines!

2024-06-18 Thread Aoife Moloney 
Hi folks,


A quick reminder that for the F41 development cycle[1], the system-wide
changes submission deadline is today, June 18th.
This does not mean your change has to be accepted, it just means that you
need to get your proposal filed by this date[2]. So if you are thinking of
proposing a change, even if it's not fully fleshed out, consider submitting
it anyway today and make use of our great community to iterate on your
proposal in real time.
The self-contained change proposal deadline is July 16th

It's important to also note that the 'testable' deadline[3] for changes is
August 6th, however please be mindful that this is also our branching date
from Rawhide so it would be preferable to have your changes landed in
rawhide and available for testing before this date.

Your change, once approved to F41, landed in Rawhide for branching and
testable, must then be 100% code complete[4] before we enter Beta Freeze on
20th August, or it will most likely need to be retargeted to F42.

Changes that are not code complete by the Beta Freeze date puts a big
strain on the folks involved with each Fedora release, so by adhering to
these dates, it helps the overall release process run much smoother, we all
benefit from a higher quality release and a slightly less stressful crunch
time at the end :) So thank you in advance for getting your changes ready
in time for these milestones, it's hugely appreciated.


Please dont hesitate to reach out with questions or if I can be of any help.


Kindest regards,
Aoife


[1] https://fedorapeople.org/groups/schedule/f-41/f-41-key-tasks.html
[2] https://docs.fedoraproject.org/en-US/program_management/changes_policy/
[3][4]
https://docs.fedoraproject.org/en-US/program_management/changes_policy/#_change_process_milestones


-- 

Aoife Moloney

Fedora Operations Architect

Fedora Project

Matrix: @amoloney:fedora.im

IRC: amoloney
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue