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&tags=mass+rebuild
Mass reb
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
after the release of Fedora 25. 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
after the release of Fedora 25. 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
ld not now be
changed for Fedora 25.
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:/
Hi Philip,
Please find the candidate composes for testing at
http://dl.fedoraproject.org/pub/alt/stage/
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
nges must now be code
complete, 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/w
The Fedora Project is pleased to announce the immediate availability of
Fedora 25 Beta, the next big step on our journey to the exciting Fedora
25 release in November.
Fedora's journey is not simply about updating one operating system with
the latest and greatest packages. It's also about innovati
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://fedoraproject.org/wiki/Releases/26/Schedule
[2] https://lists.fedoraproject.org/admin/lists/rel
done before branching Fedora 26 from rawhide[1] that is on 2017-02-28.
You can contact releng if you have any issues 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://fedoraproject.org/wiki/Releases/26/Schedule
[2
n the Fedora 26 schedule[1].
Mohan Boddu.
[1] https://fedoraproject.org/wiki/Releases/26/Schedule
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraprojec
ld not now be
changed for Fedora 26.
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:
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 one
nges must now be code complete, 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/
The Fedora Project is pleased to announce the immediate availability
of Fedora 26 Beta, the next big step on our journey to the exciting
Fedora 26 release in July.
Download the prerelease from our Get Fedora site:
* Get Fedora 26 Beta Workstation
https://getfedora.org/workstation/prerelease/
*
org/wiki/Releases/26/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/26/final/buglist
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 at
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
list.
We are hoping that it will be very helpful to all the spins, labs and
any other variant maintainers to get notified if they image build
failed and provides an easy way to find and debug the issue.
Thanks,
Mohan Boddu
Fedora Release Engineering.
[1]
https://lists.fedoraproject.org/archives/li
kerbugs/milestone/31/final/buglist
Regards,
Mohan Boddu
Release Engineering
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Cod
s://fedoraproject.org/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
_
Things should be getting better now
https://pagure.io/koji/issue/2119#comment-640757
On Sat, Apr 4, 2020 at 5:13 AM Richard W.M. Jones wrote:
>
> On Sat, Apr 04, 2020 at 12:42:29AM +0200, Miro Hrončok wrote:
> > On 03. 04. 20 13:03, Richard W.M. Jones wrote:
> > >
> > >I've been waiting on:
> >
This is a great idea, but I wouldn't recommend removing buildroot
overrides totally for one more reason than the others that are already
mentioned here. Side tags are resource intensive compared to buildroot
override as each side tag needs its own buildroot.
On Sat, Apr 4, 2020 at 5:02 PM Richard
On Tue, Apr 7, 2020 at 8:57 AM Rex Dieter wrote:
>
> Richard W.M. Jones wrote:
>
> >
> > https://bodhi.fedoraproject.org/updates/FEDORA-2020-d120de33c5
> >
> > This one is a Rawhide update from a side tag, submitted on Sunday
> > morning which has been in pending for 2 days. (As it's Rawhide it's
I guess it should be a fixed in bodhi. But for now you can remove the
builds that it's complaining about in the update.
https://github.com/fedora-infra/bodhi/issues/3991
On Tue, Apr 7, 2020 at 2:56 AM Richard W.M. Jones wrote:
>
>
> https://bodhi.fedoraproject.org/updates/FEDORA-2020-d120de33c5
On Tue, Apr 7, 2020 at 8:34 AM Fabio Valentini wrote:
>
> On Tue, Apr 7, 2020 at 8:56 AM Richard W.M. Jones wrote:
> >
> >
> > https://bodhi.fedoraproject.org/updates/FEDORA-2020-d120de33c5
> >
> > This one is a Rawhide update from a side tag, submitted on Sunday
> > morning which has been in pen
My personal favorite is Fedora 26
https://fedoraproject.org/wiki/Wallpapers#Fedora_26
I am not an artist, but the silhouette of the calming woods with the
reflection it on the lake is just *serene*.
On Fri, Apr 17, 2020 at 5:44 PM Miro Hrončok wrote:
>
> On 17. 04. 20 16:07, Kamil Paral wrote:
Sorry for the late reply, compose-tracker uses the toml file
https://pagure.io/releng/compose-tracker/blob/master/f/compose_tracker.py#_151
And the PR is merged and it should work.
On Mon, May 11, 2020 at 1:19 PM Miro Hrončok wrote:
>
> On 11. 05. 20 18:23, Ankur Sinha wrote:
> > On Mon, May 11
On Tue, May 12, 2020 at 9:14 AM Pierre-Yves Chibon wrote:
>
> On Tue, May 12, 2020 at 02:51:03PM +0200, Miro Hrončok wrote:
> > On 12. 05. 20 8:49, Pierre-Yves Chibon wrote:
> > > Finally, does everyone agree about the original request: "remove all
> > > maintainers
> > > of retired packages"? Or
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
org/wiki/Releases/31/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,
On Thu, Oct 17, 2019 at 5:34 AM Miro Hrončok wrote:
>
> Hey, I've just noticed something that I find a bit odd:
>
> This python38 update is on it's way to f31 stable:
>
> https://bodhi.fedoraproject.org/updates/FEDORA-2019-c26f535d3c
>
> This newer python38 update was submitted yesterday:
>
> http
Since there are lot of people who are showing interest, may be someone
should submit the request for a booth (probably who has done it
before) before the deadline.
We can figure out who can be the booth coordinator and stuff later on.
On Mon, Oct 28, 2019 at 11:47 AM Brian (bex) Exelbierd
wrote:
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
-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-annou
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]
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_
them from rawhide
and will not be branched.
Thanks,
Mohan Boddu.
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Condu
ng as part
of mass rebuild and sorry for the delay.
Regards,
Mohan Boddu.
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct:
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 will
nt 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]
ked for translation in Fedora-
translated projects 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] h
ssues 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-annou...@lists.fedoraproject.org
To unsubscribe send an ema
On Tue, Sep 17, 2019 at 12:30 PM Kevin Fenzi wrote:
>
> On 9/17/19 8:04 AM, Miro Hrončok wrote:
> > On 17. 09. 19 17:00, jkone...@redhat.com wrote:
> >> If that is not doable what about taking last Rawhide compose and mark
> >> that as first compose of newly branched Fedora? The only thing I'm
> >
-failures.html
Things still needing rebuilt
https://kojipkgs.fedoraproject.org/mass-rebuild/f32-need-rebuild.html
Regards
Mohan Boddu
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le
Dan and Artur,
The mass rebuild hasn't started yet, I can wait until 08:00 UTC
28-Jan-2020 before starting the mass rebuild.
If the work is not done by then, we have to run a selective rebuild later.
CC'ing Ben.
Thanks.
On Mon, Jan 27, 2020 at 3:11 PM Artur Iwicki wrote:
>
> Here's a koji scr
gt; > > > On Mon, Jan 27, 2020 at 10:25:50AM -0500, Mohan Boddu wrote:
> > > > > Hi all,
> > > > >
> > > > > Per the Fedora 32 schedule[1] we will be starting a mass rebuild for
> > > > > Fedora 32 today. We are doing a mass rebui
On Fri, Jan 31, 2020, 11:51 AM Miro Hrončok wrote:
> On 31. 01. 20 3:32, Kevin Fenzi wrote:
> > Just a few reminders for folks:
> >
> > * If your package failed to build in the mass rebuild
> > ( https://kojipkgs.fedoraproject.org/mass-rebuild/f32-failures.html )
> > and you want to fix it, pleas
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-annou
available immediately.
Thanks for understanding.
Mohan Boddu.
[1] https://fedoraproject.org/wiki/Releases/31/Schedule
On Tue, Feb 11, 2020 at 2:38 PM Miro Hrončok wrote:
>
> On 11. 02. 20 19:36, Adam Williamson wrote:
> > On Mon, 2020-02-10 at 20:05 -0500, Mohan Boddu
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-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le
We didn't pick the time at random, 14:00 UTC is the time when Fedora
release gets out. We thought if we are changing the time, we should
align it with the only other time constrained task, that is, Fedora
release.
00:00 UTC is definitely confusing for some people as they complained
about it, but 1
rked for translation in Fedora-translated projects 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#B
This should be fixed now, can you give it a try?
On Thu, Feb 27, 2020 at 10:54 AM Alejandro Álvarez Ayllón
wrote:
>
> Hello all,
>
> I am trying to build sourcextractor++, which was accepted yesterday, and
> every time I try I get the following error:
>
> BuildError: package sourcextractor++ not
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
A short history of why it happened, when we lift the freeze, we check
if all the packages that are in the stable tag are the latest builds,
if not, we tag the latest builds into koji stable tag. We do this
because, bodhi doesn't follow the latest build order while pushing
updates, so, an older vers
Thanks Adam for bringing this up, I don't want to give big
explanations on the topics, but I just want to mention a few things
here:
On Tue, Mar 17, 2020 at 2:01 PM Adam Williamson
wrote:
>
> So, today is the Fedora 32 Beta release date. If you examine the
> release announcement:
>
> https://fedo
On Wed, Mar 18, 2020 at 6:38 AM Kamil Paral wrote:
>
> On Tue, Mar 17, 2020 at 10:11 PM Mohan Boddu wrote:
>>
>> Peter and I talked about it a while ago about merging IoT into regular
>> Fedora composes. But we never got to that point. I am not sure whats
>> their p
On Mon, Nov 26, 2018 at 2:30 PM Kevin Fenzi wrote:
> On 11/26/18 10:58 AM, Peter Robinson wrote:
> > On Mon, Nov 26, 2018 at 6:53 PM Adam Williamson
> > wrote:
> >>
> >> On Mon, 2018-11-26 at 18:44 +, Peter Robinson wrote:
> >>> On Mon, Nov 26, 2018 at 4:05 PM Matthew Miller <
> mat...@fedor
On Mon, Nov 26, 2018 at 2:42 PM Adam Williamson
wrote:
> On Mon, 2018-11-26 at 11:30 -0800, Kevin Fenzi wrote:
> > On 11/26/18 10:58 AM, Peter Robinson wrote:
> > > On Mon, Nov 26, 2018 at 6:53 PM Adam Williamson
> > > wrote:
> > > > On Mon, 2018-11-26 at 18:44 +, Peter Robinson wrote:
> > >
I am still updating the EOL's in pdc, but some of them should be updated.
I will send another email once all of them are updated.
On Mon, Nov 26, 2018 at 11:10 AM Matthew Miller
wrote:
> On Mon, Nov 26, 2018 at 10:30:32AM -0500, Ben Cotton wrote:
> > The policy on the wiki[1] says "one month",
Okay, all of the eol entries for f27 in pdc should be updated now.
Please create a ticket at https://pagure.io/releng if you find any issues.
Thanks.
On Mon, Nov 26, 2018 at 7:03 PM Mohan Boddu wrote:
> I am still updating the EOL's in pdc, but some of them should be updated.
>
&g
I totally agree with Paul and Kevin.
I want to see a faster release cycle (probably rolling release) and shorter
processes to get a release out.
On Tue, Nov 27, 2018 at 3:02 PM Kevin Fenzi wrote:
> I agree with the folks in this subthread, but I think we are going to
> have to look at 'redesign
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
+1 to the change proposal.
Someone still need to submit updates in bodhi and rel-eng would be happy to
own that task and it is much simpler than what we have today.
On Mon, Dec 3, 2018 at 1:39 PM Clement Verna
wrote:
> Hi all,
>
> I would like to get feedbacks on the following proposal. Use OSB
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
T
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 mass reb
maintainers.
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://fedoraproject.org/wiki
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
On Tue, Feb 19, 2019 at 8:26 AM Mohan Boddu wrote:
> 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 un
nt in the Fedora 30 schedule[1].
Mohan Boddu.
[1] https://fedoraproject.org/wiki/Releases/30/Schedule
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
F
On Thu, Feb 28, 2019 at 2:00 PM Till Maas wrote:
> Hi friends,
>
> Brian[0] made me think about my commitments and I realized that it is
> time to step back from my FESCo seat.
>
> Thank you for your confidence in electing me last year!
>
> Kind regards
> Till
>
> [0] https://www.winglemeyer.org/
ked for translation in Fedora-
translated projects 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] h
a.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
Fedora Release Engine
org/wiki/Releases/30/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,
I retagged them, that should fix this.
On Mon, Apr 22, 2019 at 6:35 AM Kaleb Keithley wrote:
> Two more are stuck again.
>
> https://bodhi.fedoraproject.org/updates/FEDORA-2019-3b8418
> https://bodhi.fedoraproject.org/updates/FEDORA-2019-399f5bd105
>
> On Fri, Mar 22, 2019 at 3:08 PM Kevin F
They got stuck while getting signed, I retagged them and that should fix
this.
On Fri, Apr 19, 2019 at 6:47 PM Kaleb Keithley wrote:
>
> ceph-12.2.12 for f28 and f29.
>
> Happens every time.
>
> Someone please give them a kick.
>
> Thanks.
>
> --
>
> Kaleb
>
> ___
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
be enabled 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-annou...@lists.fedoraproject.org
To unsub
ked for translation in Fedora-
translated projects 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] h
gs 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.
___
test-announce mailing list -- test-
On Tue, Sep 25, 2018 at 4:35 PM Ben Cotton wrote:
> With today's Beta release, the release announcement post for Fedora
> Magazine was not ready. As a result, the announcement went out a
> little late and then only due to a drop-everything effort (thanks,
> stickster!). We have a proposal to add
On Sat, Sep 22, 2018 at 6:14 PM Miro Hrončok wrote:
> On 22.9.2018 22:47, Jerry James wrote:
> > Koji seems to be requiring 7 days in -testing for F29. Shouldn't it
> > be requiring 3 days at this point?
>
>
> I've opened https://pagure.io/releng/issue/7741 ~3 weeks ago, but I've
> got no respon
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 comp
#fedora-releng on Freenode.
Thanks,
Mohan Boddu.
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of
I am working with Cisco on fixing this. We got an email from Cisco that the
rpms are available on their CDN.
So, we pushed the repodata on our end. But it seems they are still not
available on their CDN.
On Thu, Nov 8, 2018 at 6:03 AM Peter Robinson wrote:
> https://pagure.io/releng/issue/7590
Hi,
There was some communication gap and I didn't pay much attention to that
package.
I am very much interested in maintaining the package going forward.
Sorry for the confusion that I have caused. Please create the PR's if
anything is needed,
and I will take care of it.
I will also go ahead an
m repo.
I want to get some thoughts on it before adding this feature.
Thanks,
Mohan Boddu.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.o
On Fri, Nov 16, 2018 at 9:21 AM Miro Hrončok wrote:
> On 16. 11. 18 15:15, Mohan Boddu wrote:
> > 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 &quo
This is good to know. I should enable it on some of the packages that I
maintain.
On Tue, Nov 20, 2018 at 9:25 AM Dusty Mabe wrote:
>
> I've certainly made the mistake of accidentally creating branches
> in dist-git and now being stuck with them because we can't delete
> them. Now that src.fedor
+1 to the reducing compose time, although there are many other things that
we have to do to make it even faster.
There are many good points that people are bringing up here, but I hope it
wont have any bottlenecks as that of xz compression.
Also since its a very young technology we should spend s
The 27 EOL should be tomorrow.
The n release gets EOL'ed 4 weeks after n+2 release.
But I am not sure why fedpkg is rejecting the push.
On Mon, Nov 26, 2018 at 10:06 AM Ben Cotton wrote:
> On Mon, Nov 26, 2018 at 9:48 AM John Florian
> wrote:
> >
> > At the very least, I don't recall seeing t
I am working on fixing it.
It should be fixed soon, I will send an update once its fixed.
On Mon, Nov 26, 2018 at 10:52 AM Florian Weimer wrote:
> * Ben Cotton:
>
> > On Mon, Nov 26, 2018 at 10:20 AM Mohan Boddu wrote:
> >>
> >> The 27 EOL should be tomorrow
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
n the Fedora 28 schedule[1].
Mohan Boddu.
[1] https://fedoraproject.org/wiki/Releases/28/Schedule
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraprojec
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
mar
> Greetings fellow Fedorans!
>
> I would like to kick off a general discussion about how we might gate
> packages in Rawhide. I think it would be nice to get something in place
> for the Fedora 29 timeframe.
>
> As one of the Bodhi contributors, I am inclined to suggest that we could
> use Bodhi
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 Fed
I fixed it
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-847691dbcf#comment-1723407
On Mon, Nov 9, 2020 at 5:16 PM Jie Kang wrote:
>
> Hi all,
>
> I'm attempting to submit a critical bugfix update for my jmc module in
> F33, however I found that there is an open security update whi
On Tue, Nov 10, 2020 at 9:42 AM Petr Pisar wrote:
>
> On Mon, Nov 09, 2020 at 10:35:45PM -0500, Jie Kang wrote:
> > Thank you. There is a second stream for jmc in that update:
> > jmc-latest-3320200902194158.601d93de
> >
> > Can it be removed as well?
> >
> I removed it from that update. You shoul
updates.
Regards,
Mohan Boddu.
[0]https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule
[1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send
1 - 100 of 156 matches
Mail list logo
