DevHeads.net

Postings by Mohan Boddu

Fedora 30 Beta Release Announcement

Fedora 30 Beta Released
We're excited to announce the release of Fedora 30 Beta.

A short list of highlights:

* New desktop environment options - DeepinDE and Pantheon Desktop join
GNOME, KDE Plasma, Xfce, and others

* DNF performance improvements

* The Workstation edition of Fedora 30 Beta features GNOME 3.32

* And more...

For more details about the release, read the full announcement at

* <a href="https://fedoramagazine.org/announcing-the-release-of-fedora-30-beta/" title="https://fedoramagazine.org/announcing-the-release-of-fedora-30-beta/">https://fedoramagazine.org/announcing-the-release-of-fedora-30-beta/</a>

or look for the prerelease pages in the download sections at

* <a href="https://getfedora.org/" title="https://getfedora.org/">https://getfedora.org/</a>

Since

Fedora 30 Beta Freeze

Hi all,

Today's an important day on the Fedora 30 schedule[1], with several
significant cut-offs. First of all today is
the Bodhi activation point [2]. That means that from now all Fedora 30
packages must be submitted to
updates-testing and pass the relevant requirements[3] before they will be
marked as 'stable' and moved to the
fedora repository.

Today is also the Beta freeze[4].

Fedora 30 Mass Branching

Hi All,

Fedora 30 has now been branched, please be sure to do a git pull
--rebase to pick up the new branch, as an additional reminder
rawhide/f31 has been completely isolated from previous releases, so
this means that anything you do for f30 you also have to do in the
master branch and do a build there. There will be a Fedora 30 compose
and it'll appear in
<a href="http://dl.fedoraproject.org/pub/fedora/linux/development/30/" title="http://dl.fedoraproject.org/pub/fedora/linux/development/30/">http://dl.fedoraproject.org/pub/fedora/linux/development/30/</a> once
complete. Please be sure to check it out.

Fedora 30 Mass Branching Starting Today

Hello All,

Fedora 30 will be branched from rawhide today as per the Fedora 30
schedule[1]. The process takes about a day and everything should be ready
by tomorrow. You can still be able to build packages normally until then,
but after the mass branching rawhide and F31 will be separated.

We will send another email once the branching is done.

Thanks,
Fedora Release Engineering.

[1] <a href="https://fedoraproject.org/wiki/Releases/30/Schedule" title="https://fedoraproject.org/wiki/Releases/30/Schedule">https://fedoraproject.org/wiki/Releases/30/Schedule</a>

Fedora 30 Mass Rebuild

Hi all,

Per the Fedora 30 schedule[1] we started a mass rebuild for Fedora 30
on Jan 31st 2019.

Fedora 30 Mass Rebuild

Hi all,

Per the Fedora 30 schedule[1] we are supposed to start the mass rebuild on
Jan 30th 2019, but due to known bug with gcc it got pushed by a day and
will start on Jan 31st 2019[2]. We are doing a mass rebuild for Fedora 30 for
all the changes listed in

<a href="https://pagure.io/releng/issue/8086" title="https://pagure.io/releng/issue/8086">https://pagure.io/releng/issue/8086</a>

This is a heads up that it will be done in a side tag and moved over
when completed.

Fedora 27 End Of Life

Hi,

As of the 30th of November 2018, Fedora 27 has reached its end of life
for updates and support. No further updates, including security
updates, will be available for Fedora 27. Fedora 28 will continue to receive
updates until 4 weeks after the release of Fedora 30.
The maintenance schedule of Fedora releases is documented on the
Fedora Project wiki [0].

Giving same acls to new modular repos as that of their respective rpms repos

Hello,

We got a suggestion about giving same acls of rpm when creating new module
dist-git which matches the rpm.

The plan is to give "main admin" permission to the requester of the new
module repo and then giving the same permissions as that of the maintainers
from its matching rpm repo.

I want to get some thoughts on it before adding this feature.

Thanks,
Mohan Boddu.

Bodhi update pushes are now automated

Hello all,

For a long time now updates are pushed manually everyday. It was
troublesome and someone has to own it for a week and look after it.

Now, the pushes are automated and are pushed everyday at 00:00 UTC. If
anything fails there will be an oncall person (same person who used to do
the pushes) who will take care of the failure.

During release freezes these automated pushes are disabled and are manually
pushed by RelEng/Infra.

Fedora 29 Final Freeze

Hi all,

Today, October 09th 2018, is an important day on the Fedora 29
schedule [1], with significant cut-offs.

Today we have the Final Freeze [2]. This means that only packages
which fix accepted blocker or freeze exception bugs [3][4][5] will be
marked as 'stable' and included in the Final composes.

Fedora 29 Beta Release Announcement

Fedora 29 Beta Released
We're excited to announce the release of Fedora 29 Beta.

A short list of highlights:

* Modularity for all.

* The Workstation edition of Fedora 29 Beta features GNOME 3.30.

* Fedora Atomic Workstation was rebranded as Fedora Silverblue.

* And more...

For more details about the release, read the full announcement at

* <a href="https://fedoramagazine.org/announcing-fedora-29-beta/" title="https://fedoramagazine.org/announcing-fedora-29-beta/">https://fedoramagazine.org/announcing-fedora-29-beta/</a>

or look for the prerelease pages in the download sections at

* <a href="https://getfedora.org/" title="https://getfedora.org/">https://getfedora.org/</a>

Since this is a Beta release, we expect that you may encounter bugs or
m

Fedora 29 Beta Freeze

Hi all,

Today's an important day on the Fedora 29 schedule[1], with several
significant cut-offs. First of all today is
the Bodhi activation point [2]. That means that from now all Fedora 29
packages must be submitted to
updates-testing and pass the relevant requirements[3] before they will be
marked as 'stable' and moved to the
fedora repository.

Today is also the Beta freeze[4].

Fedora 29 Mass Branching

Hi All,

Fedora 29 has now been branched, please be sure to do a git pull
--rebase to pick up the new branch, as an additional reminder
rawhide/f30 has been completely isolated from previous releases, so
this means that anything you do for f29 you also have to do in the
master branch and do a build there. There will be a Fedora 29 compose
ASAP and it'll appear
<a href="http://dl.fedoraproject.org/pub/fedora/linux/development/29/" title="http://dl.fedoraproject.org/pub/fedora/linux/development/29/">http://dl.fedoraproject.org/pub/fedora/linux/development/29/</a>
<http://dl.fedoraproject.org/pub/fedora/linux/development/28/> once
complete. Please be sure to check it out.

Fedora 29 Mass Rebuild

Hi all,

Per the Fedora 29 schedule[1] we will be starting a mass rebuild for Fedora
29 very shortly. We are doing a mass rebuild for Fedora 29 for all the
changes listed in

<a href="https://pagure.io/releng/issue/7480" title="https://pagure.io/releng/issue/7480">https://pagure.io/releng/issue/7480</a>

we will start the mass rebuild on 2018-07-11

This is a heads up that it will be done in a side tag and moved over
when completed.

Fedora 26 End Of Life

As of the 29th of May 2018, Fedora 26 has reached its end of life
for updates and support. No further updates, including security
updates, will be available for Fedora 26. Fedora 27 will continue to receive
updates until approximately one month after the release of Fedora 29.
The maintenance schedule of Fedora releases is documented on the
Fedora Project wiki [0].