REMINDER: Submission deadline for Changes of Fedora 29 requiring mass rebuild takes effect in one week

Hi everyone!

The submission deadline for Changes of Fedora 29 [1], requiring mass
rebuild, takes effect in one week on June 19th. All the Changes
requiring mass rebuild sent for review after this deadline are going
to be moved to Fedora 30 release.
The mass rebuild it self is planned on July 11th.

The deadline for System Wide Changes which do not need the mass
rebuild is planned on July 3rd.

If your Change proposal needs mass rebuild, please submit it by the
deadline, earlier better. In case you'll need any help with your
Change proposals, feel free to contact me.

[1] <a href="" title=""></a>

Best Regards,


Re: REMINDER: Submission deadline for Changes of Fedora 29 requi

By Alain Vigne at 06/12/2018 - 07:10

I was wondering how introduction of a new package enters such schedule [1] ?
More specifically, when is the deadline for a new package to enter Fedora
29 ?

I recall my introduction from 5 days ago, stating I volunteer to maintain a
new EDA package (and co-maintain others ?) :
I am Alain, a French EE engineer using Fedora 28 and EDA open source tools,
as an hobby.

I am part of the pcb-rnd developer upstream
<a href="" title=""></a>
and was able to produce a .spec file + SRPM rpm file, and COPR successful
<a href="" title=""></a>

Now, I am looking for a sponsor to get this package into Fedora. I filled
this bug:
<a href="" title=""></a>

I volunteer to be the package maintainer, have read the guidelines and
acknowledge responsibilities requested for such a task.
My FAS username is: avigne

This package could also be part of FEL (Fedora Electronic Lab) spin, to be
revived ?

Hoping for some positive feed-back...
Best regards

Re: REMINDER: Submission deadline for Changes of Fedora 29 requi

By Kevin Fenzi at 06/13/2018 - 14:56

On 06/12/2018 04:10 AM, Alain Vigne wrote:
There's no hard deadline, new packages enter any Fedora version anytime.
In already released (or very close to release, ie, Final Freeze)
fedora's new packages only go to the 'updates-testing' and then
'updates' repos. In branched/under development ones they go to the base
Everything repo while that version is under development, then new
versions go to updates/updates-testing after release.

Hopefully that answers the question?
You'll need to wait for that package to get reviewed...
It could be.