.
Finally, today is the 'completion deadline' Change Checkpoint[8],
meaning that Fedora 25 Changes must now be 'feature complete or close
enough to completion that a majority of its functionality can be
tested'.
Regards
Mohan Boddu
[1] https://fedoraproject.org/wiki/Releases/25/Schedule
[2] https
, meaning all the code required to enable to the new change is
finished. The level of code completeness is reflected as tracker bug
state ON_QA. The change does not have to be fully tested by this
deadline'.
Regards
Mohan Boddu
[1] https://fedoraproject.org/wiki/Releases/25/Schedule
[2] https
one month after the release of Fedora 26.
The maintenance schedule of Fedora releases is documented on the
Fedora Project wiki [1]. The Fedora Project wiki also contains
instructions [2] on how to upgrade from a previous release of Fedora
to a version receiving updates.
Mohan Boddu.
[0]https
The Fedora Project is pleased to announce the immediate availability of
the Fedora 26 Alpha, an important milestone on the road to our Fedora 26
release in June.
Download the prerelease from our Get Fedora site:
- Get Fedora 26 Alpha Workstation
- Get Fedora 26 Alpha Server
Or, check out
.
Finally, today is the 'completion deadline' Change Checkpoint[8],
meaning that Fedora 26 Changes
must now be 'feature complete or close enough to completion that a
majority of its functionality can be tested'.
Regards
Mohan Boddu
[1] https://fedoraproject.org/wiki/Releases/26/Schedule
[2] https
in the Fedora 26 schedule[1].
Mohan Boddu.
[1] https://fedoraproject.org/wiki/Releases/26/Schedule
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Hi,
We have a ticket on how to clean up packages with broken deps:
https://pagure.io/releng/issue/6877
We had a discussion about this issue in our releng meeting on Jul 10th
2017. The problem is that there is no good way of solving this issue, but
we came up two options:
1. Blocking the pkgs
month after the release of Fedora 27. The maintenance
schedule of Fedora releases is documented on the Fedora Project wiki [1].
The Fedora Project wiki also contains instructions [2] on how to upgrade
from a previous release of Fedora to a version receiving updates. Mohan
Boddu.
[0]https
Fedora 27 Beta Released
---
We're excited to announce the release of Fedora 27 Beta.
A short list of changes:
The Workstation edition of Fedora 27 Beta features GNOME 3.26.
LibreOffice is updated to LibreOffice 5.4.
Fedora Atomic 27 now defaults to a more simple container
that Fedora 27 Changes must now be ‘feature complete or close enough to
completion that a majority of its functionality can be tested’.
Regards
Mohan Boddu.
[1] https://fedoraproject.org/wiki/Releases/27/Schedule
[2] https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling
[3] https
/Schedule [2]
https://fedoraproject.org/wiki/Milestone_freezes [3]
https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [4]
https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [5]
https://qa.fedoraproject.org/blockerbugs/milestone/27/final/buglist
Regards, Mohan Boddu
in the Fedora 28 schedule[1].
Mohan Boddu.
[1] https://fedoraproject.org/wiki/Releases/28/Schedule
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
nabled in couple of weeks time when we hit
Beta change freeze point in the Fedora 29 schedule[1].
Mohan Boddu.
[1] https://fedoraproject.org/wiki/Releases/29/Schedule
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscrib
should not now be changed for Fedora 29.
Mohan Boddu
[1] https://fedoraproject.org/wiki/Releases/29/Schedule
[2] https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling
[3] https://fedoraproject.org/wiki/Updates_Policy#Branched_release
[4] https://fedoraproject.org/wiki/Milestone_freezes
[5
AM Mohan Boddu wrote:
> 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
>
> https://pagure.io/releng/issue/7480
>
> we will start the
-failures.html
Things still needing rebuilt
https://kojipkgs.fedoraproject.org/mass-rebuild/f29-need-rebuild.html
Regards
Mohan Boddu
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce
.
Thanks,
Fedora Release Engineering.
On Wed, Jul 11, 2018 at 1:55 PM Mohan Boddu wrote:
> Hi all,
>
> We are delaying the mass rebuild as people are still working on
> binutils 2.31 change (https://fedoraproject.org/wiki/Changes/BINUTILS231).
>
> At this point, we want to re-eval
Fedora 28 Beta Released
---
We're excited to announce the release of Fedora 28 Beta.
A short list of highlights:
* Modular Repository for Fedora Server
* The Workstation edition of Fedora 28 Beta features GNOME 3.28.
* 64-bit Arm (Aarch64) now a primary architecture for
Hi all,
Today’s an important day on the Fedora 28 schedule[1], with several
significant cut-offs. First of all today is the Bodhi activation point [2].
That means that from now all Fedora 28 packages must be submitted to
updates-testing and pass the relevant requirements[3] before they will be
on
#fedora-releng on Freenode.
Thanks,
Mohan Boddu.
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code
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
/
Since this is a Beta release, we expect that you may encounter bugs or
missing features. To report issues encountered during testing, contact the
Fedora QA team via the mailing list or in #fedora-qa on Freenode.
Regards,
Mohan Boddu
Fedora Release Engineering
in the Fedora 30 schedule[1].
Mohan Boddu.
[1] https://fedoraproject.org/wiki/Releases/30/Schedule
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora
should not now be changed for Fedora 30.
Mohan Boddu
[1] https://fedoraproject.org/wiki/Releases/30/Schedule
[2] https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling
[3] https://fedoraproject.org/wiki/Updates_Policy#Branched_release
[4] https://fedoraproject.org/wiki/Milestone_freezes
[5
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
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
https://pagure.io/releng/issue/8086
Hi all,
Fedora 30 Mass Rebuild will start in few minutes. We are preparing for the
final steps and will run mass rebuild once everything is in place.
On Wed, Jan 30, 2019 at 4:02 AM Mohan Boddu wrote:
> Hi all,
>
> Per the Fedora 30 schedule[1] we are supposed to start the mas
/Schedule
[2] https://fedoraproject.org/wiki/Milestone_freezes
[3] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
[4] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
[5] https://qa.fedoraproject.org/blockerbugs/milestone/30/final/buglist
Regards,
Mohan Boddu
Release
schedule of Fedora releases is documented on the
Fedora Project wiki [0]. The Fedora Project wiki also contains
instructions [1] on how to upgrade from a previous release of Fedora
to a version receiving updates.
Regards,
Mohan Boddu.
[0]
https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle
as part
of mass rebuild and sorry for the delay.
Regards,
Mohan Boddu.
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https
in the Fedora 31 schedule[1].
Two things to remember:
1. The modules are still building for the new platform:f32.
2. Since the signing of rpms is not done yet for the new f32 builds, you
might expect failed composes for the next couple of days.
Thanks for understanding.
Mohan Boddu.
[1] https
Hello All,
Fedora 31 will be branched from rawhide today as per the Fedora 31
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
rawhide
and will not be branched.
Thanks,
Mohan Boddu.
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https
should not now be changed for Fedora 31.
Mohan Boddu
[1] https://fedoraproject.org/wiki/Releases/31/Schedule
[2] https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling
[3] https://fedoraproject.org/wiki/Updates_Policy#Branched_release
[4] https://fedoraproject.org/wiki/Milestone_freezes
[5
encountered during testing, contact the
Fedora QA team via the mailing list or in #fedora-qa on Freenode.
Regards,
Mohan Boddu
Fedora Release Engineering.
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email
Hello all,
As per the FTBFS policy [1], we started the retirement of the packages that
have been FTBFS since F30 mass rebuild. Please follow the unretirement
process [2] if you are planning to re-add the package to Fedora.
[1]
-failures.html
Things still needing rebuilt
https://kojipkgs.fedoraproject.org/mass-rebuild/f31-need-rebuild.html
[1] https://fedoraproject.org/wiki/Releases/31/Schedule
Regards,
Mohan Boddu
___
devel-announce mailing list -- devel-announce
. The
maintenance schedule of Fedora releases is documented on the Fedora
Project wiki [0]. The Fedora Project wiki also contains instructions
[1] on how to upgrade from a previous release of Fedora to a version
receiving updates.
Mohan Boddu.
[0]
https://fedoraproject.org/wiki
/Schedule
[2] https://fedoraproject.org/wiki/Milestone_freezes
[3] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
[4] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
[5] https://qa.fedoraproject.org/blockerbugs/milestone/31/final/buglist
Regards,
Mohan Boddu
Release
should
not now be changed for Fedora 32.
Mohan Boddu
[1] https://fedorapeople.org/groups/schedule/f-32/f-32-key-tasks.html
[2] https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling
[3] https://fedoraproject.org/wiki/Updates_Policy#Branched_release
[4] https://fedoraproject.org/wiki
updated to
reflect the changed time.
[1] https://fedorapeople.org/groups/schedule/f-32/f-32-key-tasks.html
Thanks,
Mohan Boddu.
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le
branching rawhide and F32 will be separated.
We will send another email once the branching is done.
Thanks,
Mohan Boddu.
[1] https://fedorapeople.org/groups/schedule/f-32/f-32-key-tasks.html
___
devel-announce mailing list -- devel-announce
g/wiki/QA:SOP_freeze_exception_bug_process
> [5] https://qa.fedoraproject.org/blockerbugs/milestone/31/final/buglist
Correcting the url:
[5] https://qa.fedoraproject.org/blockerbugs/milestone/32/final/buglist
>
> Regards,
> Mohan Boddu
> Release Engineering
/final/buglist
Regards,
Mohan Boddu
Release Engineering
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https
for the prerelease pages in the download sections at
* https://getfedora.org/
Since this is a Beta release, we expect that you may encounter bugs or
missing features. To report issues encountered during testing, contact
the Fedora QA team via the mailing list or in #fedora-qa on Freenode.
Regards,
Mohan Boddu
/final/buglist
Regards,
Mohan Boddu
Release Engineering
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https
...@lists.fedoraproject.org mailing list or
in #fedora-qa on Freenode.
Regards,
Mohan Boddu
Fedora Release Engineering.
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
. The
maintenance schedule of Fedora releases is documented on the Fedora
Project wiki [0]. The Fedora Project wiki also contains instructions
[1] on how to upgrade from a previous release of Fedora to a version
receiving updates.
Mohan Boddu.
[0]
https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle
Hello All,
We had an issue today as some people were unable to push to dist-git
f31 branches, it was caused by setting a wrong date in pdc. It has
been fixed now and people can push to f31 branches.
More info at https://pagure.io/fedora-infrastructure/issue/9325
Sorry for the trouble that this
Hi all,
The mass rebuild is postponed to next Monday 27th July 2020 since a
couple of changes haven't landed yet.
For more information, please look at https://pagure.io/fesco/issue/2451
We will keep you posted if anything changes.
Thanks.
On Mon, Jul 20, 2020 at 5:38 PM Mohan Boddu wrote
rebuildling of modules and FTBFS bugs will be filed shortly.
Please be sure to let releng know if you see any bugs in the
reporting. You can contact releng in #fedora-releng on freenode, by
dropping an email to our list[2] or filing an issue in pagure[3]
Regards,
Mohan Boddu.
[1] https
.
Thanks for understanding.
Mohan Boddu.
[1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html
On Sun, Aug 9, 2020 at 3:16 PM Mohan Boddu wrote:
>
> Hello All,
>
> Fedora 33 will be branched from rawhide on August 11th 2020 as per the
> Fedora 33 schedule[1]. Th
will be separated.
We will send another email once the branching is done.
Thanks,
Mohan Boddu.
[1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe
Mohan Boddu
4:32 PM (1 hour ago)
to devel-announce
Hi all,
Per the Fedora 33 schedule[1] we will start a mass rebuild for Fedora 33
on Jul 22nd 2020. We will run a mass rebuild for Fedora 33 for the
changes listed in:
https://pagure.io/releng/issues?status=Open=mass+rebuild
Mass rebuild
.
Mohan Boddu.
[0]
https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule
[1] https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/
On Fri, Nov 20, 2020 at 10:26 AM Mohan Boddu wrote:
>
> Hello all,
>
> Fedora 31 will go end of life for updates
This is great news, thanks to everyone who worked on this project.
On Thu, Dec 10, 2020 at 5:44 AM Mark O'Brien wrote:
>
> All,
> We are very happy to announce that we now have AArch64 support for flatpak
> and container fedpkg builds in production!
>
> By default all flatpak and container
updates.
Regards,
Mohan Boddu.
[0]https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule
[1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
in the
reporting. You can contact releng in #fedora-releng on freenode, by
dropping an email to our list[2] or filing an issue in pagure[3]
Regards,
Mohan Boddu.
[1] https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html
[2] https://lists.fedoraproject.org/admin/lists/rel
you posted with any further developments.
Thanks.
On Fri, Jan 15, 2021 at 2:31 PM Mohan Boddu wrote:
>
> Hi all,
>
> Per the Fedora 34 schedule[1] we will start a mass rebuild for Fedora 34
> on Jan 20th 2021. We will run a mass rebuild for Fedora 34 for the
> changes li
Hi all,
While working on master to rawhide change [0], we made changes to
fedpkg and other tools, while we thought of coordinating about when to
release it (post mass rebuild) fedpkg-1.40-2 got released with the
changes in F33 and rawhide. This has issues with processing new repo
requests [1].
I
Hello everyone,
We are about to start the change process. As previously mentioned,
pushes to 'master' branch will be disabled, once we made the changes,
we will send another email at which point you need to run `git fetch
-p` or checkout 'rawhide' branch and you can start building packages
in the
.
Mohan Boddu.
[0]
https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule
[1] https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
will be separated.
We will send another email once the branching is done.
Thanks,
Mohan Boddu.
[1] https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send
.
Thanks for understanding.
[1] https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html
On Mon, Feb 8, 2021 at 11:39 AM Mohan Boddu wrote:
>
> Hello All,
>
> Fedora 34 will be branched from rawhide on Feb 09th 2021 as per the
> Fedora 34 schedule[1]. The process ta
,
Mohan Boddu
Fedora Release Engineering.
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US
/final/buglist
Regards,
Mohan Boddu
Release Engineering
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https
Mohan Boddu
[1] https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html
[2] https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling
[3] https://fedoraproject.org/wiki/Updates_Policy#Branched_release
[4] https://fedoraproject.org/wiki/Milestone_freezes
[5] https://fedoraproject.org/wiki
Hi All,
Fedora 35 has now been branched, please be sure to do a git pull
--rebase to pick up the new branch, as an additional reminder
rawhide/f36 has been completely isolated from previous releases, so
this means that anything you do for f35 you also have to do in the
rawhide branch and do a
issues encountered during testing, contact
the Fedora QA team via the t...@lists.fedoraproject.org mailing list or
in #fedora-qa on Libera Chat.
Regards,
Mohan Boddu
Fedora Release Engineering.
___
devel-announce mailing list -- devel-announce
/buglist
Regards,
Mohan Boddu
Release Engineering
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en
updates.
Regards,
Mohan Boddu.
[0]https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule
[1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
71 matches
Mail list logo
