https://bugzilla.redhat.com/show_bug.cgi?id=1106166
Jitka Plesnikova changed:
What|Removed |Added
Status|NEW |CLOSED
CC|
If F31 is delayed by 6 months and F30 is supported for 6 months longer,
does it mean F29 *also* automatically gets a longer cycle since it by
policy becomes EOL when F31 is out + 1 month?
Can we EOL F29 6 months before F31 is out to not have *two* long term
branches to maintain?
--
Kalev
https://bugzilla.redhat.com/show_bug.cgi?id=1651166
Fedora Update System changed:
What|Removed |Added
Status|MODIFIED|ON_QA
--- Comment #2 from
No missing expected images.
Failed openQA tests: 1/2 (x86_64)
ID: 312879 Test: x86_64 AtomicHost-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/312879
Passed openQA tests: 1/2 (x86_64)
--
Mail generated by check-compose:
On 11/28/18 1:32 AM, Kevin Fenzi wrote:
I agree with the folks in this subthread, but I think we are going to
have to look at 'redesigning' things more than just 'optimizing'.
+1. At the same time, we should also ensure that Devel,QE,Infra,RelEng..
all equal stake holders and are hand in
The following Fedora EPEL 7 Security updates need testing:
Age URL
171 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-3835d39d1a
unrtf-0.21.9-8.el7
122 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-f9d6ff695a
bibutils-6.6-1.el7 ghc-hs-bibutils-6.6.0.0-1.el7
https://bugzilla.redhat.com/show_bug.cgi?id=1647620
Fedora Update System changed:
What|Removed |Added
Status|ON_QA |CLOSED
Resolution|---
On 11/27/18 11:39 AM, Owen Taylor wrote:
We can definitely talk about whether moving to a slower cadence for
certain parts of the base platform. But people don't judge Fedora on
how beautifully we maintain glibc and gcc - they mostly judge it by
installing it on a laptop and seeing how well it
https://bugzilla.redhat.com/show_bug.cgi?id=1612860
Fedora Update System changed:
What|Removed |Added
Status|ON_QA |CLOSED
Fixed In
https://bugzilla.redhat.com/show_bug.cgi?id=1650151
Fedora Update System changed:
What|Removed |Added
Fixed In Version|perl-Dancer2-0.207000-1.fc3 |perl-Dancer2-0.207000-1.fc3
No missing expected images.
Failed openQA tests: 1/2 (x86_64)
ID: 312876 Test: x86_64 AtomicHost-dvd_ostree-iso install_default
URL: https://openqa.fedoraproject.org/tests/312876
Passed openQA tests: 1/2 (x86_64)
--
Mail generated by check-compose:
https://fedorapeople.org/groups/389ds/ci/nightly/2018/11/28/report-389-ds-base-1.4.0.19-20181128gita990d04.fc29.x86_64.html
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to
On Tue, 2018-11-27 at 20:42 -0500, Mike Miller wrote:
> The python2-pyyaml package was missing a file, weird.
> rpm -V python2-pyyaml-3.12-10.fc28.x86_64
> missing /usr/lib64/python2.7/site-packages/PyYAML-3.12-py2.7.egg-info
>
> Running "dnf reinstall python2-pyyaml-3.12-10.fc28.x86_64"
The python2-pyyaml package was missing a file, weird.
rpm -V python2-pyyaml-3.12-10.fc28.x86_64
missing /usr/lib64/python2.7/site-packages/PyYAML-3.12-py2.7.egg-info
Running "dnf reinstall python2-pyyaml-3.12-10.fc28.x86_64" fixed it.
Thanks for the help!
On Tue, Nov 27, 2018 at 8:26 PM
> "MM" == Mike Miller writes:
MM> I have installed the latest fedpkg, fedpkg-1.35-1.fc28.noarch. Do I
MM> need to upgrade to 29? I thought fedpkg would still work on 28.
I'm still on F28 (for another hour or so) and have no problems running
fedpkg.
fedpkg-1.35-1.fc28.noarch
Hello - I am trying to update a package on Fedora 28 but am getting this
error any time I try to run fedpkg:
Traceback (most recent call last):
File "/usr/bin/fedpkg", line 6, in
from pkg_resources import load_entry_point
File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py",
On Tue, Nov 27, 2018 at 5:39 PM Miro Hrončok wrote:
>
> On 27. 11. 18 23:25, Christopher wrote:
> > Okay, so, in https://src.fedoraproject.org , repos seem to have two
> > URLs for SSH access.
> > One is referred to as "Pull Requests" in the "helpful" "Clone"
> > dropdown menu. However, I cannot
https://bugzilla.redhat.com/show_bug.cgi?id=1475784
Emmanuel Seyman changed:
What|Removed |Added
CC||emman...@seyman.fr
https://bugzilla.redhat.com/show_bug.cgi?id=1456817
Emmanuel Seyman changed:
What|Removed |Added
CC||emman...@seyman.fr
External Bug
eseyman opened a new pull-request against the project: `perl-Email-MessageID`
that you are following:
``
Remove unneeded requirement
``
To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Email-MessageID/pull-request/1
___
On 11/27/2018 10:39 AM, Owen Taylor wrote:
We can definitely talk about whether moving to a slower cadence for
certain parts of the base platform. But people don't judge Fedora on
how beautifully we maintain glibc and gcc - they mostly judge it by
installing it on a laptop and seeing how well it
On 27. 11. 18 23:25, Christopher wrote:
Okay, so, in https://src.fedoraproject.org , repos seem to have two
URLs for SSH access.
One is referred to as "Pull Requests" in the "helpful" "Clone"
dropdown menu. However, I cannot figure out what this is for.
If the origin is:
Okay, so, in https://src.fedoraproject.org , repos seem to have two
URLs for SSH access.
One is referred to as "Pull Requests" in the "helpful" "Clone"
dropdown menu. However, I cannot figure out what this is for.
If the origin is:
ssh://ctubb...@pkgs.fedoraproject.org/rpms/zookeeper.git
Then
On Tuesday, November 27, 2018, Owen Taylor wrote:
> On Tue, Nov 27, 2018 at 10:51 AM Stephen Gallagher
> wrote:
> > As came up in another part of the earlier thread, I think this is an
> > opportunity for Modularity. For those things like GNOME that want to
> > rev mid-release, if they shipped
A new Fedora Atomic Host update is available via an OSTree update:
Version: 29.20181126.0
Commit(x86_64): a10e5df10dd29683fd9b08df3cbd562b034768b4ca8ad52ba5c7620b789eb62c
Commit(aarch64):
36f7f42a1933cab67434b06d084fa7b79b146ff1a32eebcd8ef3cafeff12c83c
Commit(ppc64le):
On 27/11/18 19:45, Miroslav Suchý wrote:
> Dne 26. 11. 18 v 16:57 Ben Cotton napsal(a):
>> Bugzilla 5.0 introduces a new REST endpoint to replace XML-RPC and
>> JSON-RPC. The XML-RPC and JSON-RPC APIs will remain available.
>
> Before someone jumps into porting their code to the new REST API (my
Hello,
I'm orphaning TinyCA2, since it is accumulating bug-reports while
upstream is no longer maintained, recently even vanished. Plus I've
switched to XCA, thus no longer use TinyCA2.
Given state of upstream, I'm not sure whether anyone would be interested
to take over maintenance of he
Hello,
I'm no longer using it and don't have the cycles to maintain it anymore.
https://src.fedoraproject.org/rpms/scite
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
On Tue, 2018-11-27 at 12:09 +, rawh...@fedoraproject.org wrote:
> Announcing the creation of a new nightly release validation test event
> for Fedora 30 Rawhide 20181127.n.0. Please help run some tests for this
> nightly compose if you have time. For more information on nightly
On Tue, 2018-11-27 at 19:30 +, Peter Robinson wrote:
> On Tue, Nov 27, 2018 at 6:26 PM Paul Frields wrote:
> > On Tue, Nov 27, 2018 at 9:50 AM Dennis Gilmore wrote:
> > [...snip...]
> > > > The customers RH serves have specific expectations, and in part that
> > > > dictates how delivery
I agree with the folks in this subthread, but I think we are going to
have to look at 'redesigning' things more than just 'optimizing'.
ie, collect all our inputs and outputs and things we need to do in the
process and figure out how to make it modular (no relation) so we can
look at just a
On Tue, Nov 27, 2018 at 6:26 PM Paul Frields wrote:
>
> On Tue, Nov 27, 2018 at 9:50 AM Dennis Gilmore wrote:
> [...snip...]
> > > The customers RH serves have specific expectations, and in part that
> > > dictates how delivery tooling is done. Binding the community to that
> > > may be
On Tue, 2018-11-27 at 11:56 +0100, Vít Ondruch wrote:
> Does that mean that Bodhi will be finally enabled for Rawhide or not?
> Because otherwise I can't see how Bodhi is related here.
Indeed, the plan is to make Bodhi manage Rawhide as well.
signature.asc
Description: This is a digitally
On Tue, Nov 27, 2018 at 9:59 AM Owen Taylor wrote:
> A lot of discussion about improving the compose process seem to end up
> with a "reality check" - that ideas have already been tried but don't
> work because of requirements a) b) c) d). You can't have the pony, but
> maybe if a lot of effort
https://bugzilla.redhat.com/show_bug.cgi?id=1435834
Ed S. changed:
What|Removed |Added
Component|perl-Carton |perl-Carton
Version|27
On Tue, Nov 27, 2018 at 1:40 PM Owen Taylor wrote:
>
> We can definitely talk about whether moving to a slower cadence for
> certain parts of the base platform. But people don't judge Fedora on
> how beautifully we maintain glibc and gcc - they mostly judge it by
> installing it on a laptop and
https://bugzilla.redhat.com/show_bug.cgi?id=1207174
Paul Howarth changed:
What|Removed |Added
Version|27 |rawhide
--
You are receiving this
On Tue, Nov 27, 2018 at 12:19 PM Josh Boyer wrote:
> On Tue, Nov 27, 2018 at 11:21 AM Owen Taylor wrote:
> > On Tue, Nov 27, 2018 at 11:05 AM Josh Boyer
> > wrote:
[...snip...]
> > > I completely disagree. Our release process and tooling is built on
> > > heroism and tech debt. At some
We can definitely talk about whether moving to a slower cadence for
certain parts of the base platform. But people don't judge Fedora on
how beautifully we maintain glibc and gcc - they mostly judge it by
installing it on a laptop and seeing how well it works. And it doesn't
really matter how
No missing expected images.
Failed openQA tests: 75/142 (x86_64), 21/24 (i386), 1/2 (arm)
New failures (same test did not fail in Rawhide-20181126.n.0):
ID: 312649 Test: x86_64 Server-dvd-iso install_repository_nfs_variation
URL: https://openqa.fedoraproject.org/tests/312649
ID: 312650
https://bugzilla.redhat.com/show_bug.cgi?id=1435834
--- Comment #9 from Ben Cotton ---
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30 Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from
https://bugzilla.redhat.com/show_bug.cgi?id=1207174
--- Comment #7 from Ben Cotton ---
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30 Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from
https://bugzilla.redhat.com/show_bug.cgi?id=1106166
--- Comment #10 from Ben Cotton ---
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30 Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from
https://bugzilla.redhat.com/show_bug.cgi?id=1472172
--- Comment #5 from Ben Cotton ---
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30 Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from
https://bugzilla.redhat.com/show_bug.cgi?id=1475784
--- Comment #2 from Ben Cotton ---
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30 Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from
On Tue, Nov 27, 2018 at 9:50 AM Dennis Gilmore wrote:
[...snip...]
> > The customers RH serves have specific expectations, and in part that
> > dictates how delivery tooling is done. Binding the community to that
> > may be counterproductive. This is especially true now that RHEL 8 Beta
> > is
On 11/27/18 10:13 AM, Josh Boyer wrote:
On Tue, Nov 27, 2018 at 11:21 AM Owen Taylor wrote:
On Tue, Nov 27, 2018 at 11:05 AM Josh Boyer wrote:
On Tue, Nov 27, 2018 at 10:13 AM Owen Taylor wrote:
But for the next thousand or so Fedora developers, the release cycle
is actually not a big
https://bugzilla.redhat.com/show_bug.cgi?id=1487209
--- Comment #3 from Ben Cotton ---
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30 Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from
On 11/27/18 7:54 AM, Ben Cotton wrote:
On Tue, Nov 27, 2018 at 8:21 AM Justin Forbes wrote:
Long cycles have been done before, and will be done again, it has been
4 or 5 years since the last one. I think skipping to a yearly cadence
for every release isn't such a great idea. There are
Dear all,
You are kindly invited to the meeting:
EPEL Steering Co on 2018-11-28 from 18:00:00 to 19:00:00 GMT
At freenode@fedora-meeting
The meeting will be about:
This is the weekly EPEL Steering Committee Meeting. Agenda is in the
https://bugzilla.redhat.com/show_bug.cgi?id=1532250
--- Comment #6 from Ben Cotton ---
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30 Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from
On Tue, Nov 27, 2018 at 10:51 AM Stephen Gallagher wrote:
> As came up in another part of the earlier thread, I think this is an
> opportunity for Modularity. For those things like GNOME that want to
> rev mid-release, if they shipped the 3.34 release as new stream, those
> that want to move to
On Tue, Nov 27, 2018 at 4:39 PM Owen Taylor wrote:
>
> One of the key parts of making a decision to delay/skip F31 is
> figuring out, ahead of the decision, what the expected experience is
> for users and packagers. Does F30 have normal stability, or do we try
> to keep users happy by moving
On Tue, Nov 27, 2018 at 11:21 AM Owen Taylor wrote:
>
> On Tue, Nov 27, 2018 at 11:05 AM Josh Boyer wrote:
> > On Tue, Nov 27, 2018 at 10:13 AM Owen Taylor wrote:
> > > But for the next thousand or so Fedora developers, the release cycle
> > > is actually not a big deal - not something that
On 27. 11. 18 16:49, Stephen Gallagher wrote:
On Tue, Nov 27, 2018 at 10:40 AM Owen Taylor wrote:
One of the key parts of making a decision to delay/skip F31 is
figuring out, ahead of the decision, what the expected experience is
for users and packagers. Does F30 have normal stability, or do
https://bugzilla.redhat.com/show_bug.cgi?id=1456817
Edgar Hoch changed:
What|Removed |Added
Version|27 |29
--- Comment #5 from Edgar Hoch ---
On Tue, Nov 27, 2018 at 10:49:55AM -0500, Stephen Gallagher wrote:
> As came up in another part of the earlier thread, I think this is an
> opportunity for Modularity. For those things like GNOME that want to
> rev mid-release, if they shipped the 3.34 release as new stream, those
> that want to
https://bugzilla.redhat.com/show_bug.cgi?id=1456817
--- Comment #4 from Ben Cotton ---
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30 Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from
Unfortunately due to some reasons I can't or don't want to modularize some
packages.
What should I do in this case?
On Tue, Nov 27, 2018, 16:59 Stephen Gallagher On Tue, Nov 27, 2018 at 10:40 AM Owen Taylor wrote:
> >
> > One of the key parts of making a decision to delay/skip F31 is
> >
Hey Jason,
On Tue, Nov 27, 2018 at 9:42 AM Jason L Tibbitts III
wrote:
> > "SS" == Salman Siddiqui writes:
>
> SS> I accidentally submitted a Koji build for 4 packages [1] that
> SS> are not supposed to be packaged for Rawhide.
>
> Are they EPEL only packages are something?
>
The packages
On Tue, 27 Nov 2018, Manuel Wolfshant wrote:
On 11/27/18 3:45 PM, m...@tdiehl.org wrote:
On Mon, 26 Nov 2018, Stephen John Smoogen wrote:
On Mon, 26 Nov 2018 at 11:00, Christopher
wrote:
On Mon, Nov 26, 2018 at 7:12 AM Stephen John Smoogen
wrote:
On Mon, 26 Nov 2018 at 01:03,
On Tue, 27 Nov 2018 at 17:23, Owen Taylor wrote:
>
> On Tue, Nov 27, 2018 at 11:05 AM Josh Boyer wrote:
> > On Tue, Nov 27, 2018 at 10:13 AM Owen Taylor wrote:
> > > But for the next thousand or so Fedora developers, the release cycle
> > > is actually not a big deal - not something that takes
=
#fedora-meeting-3: Weekly Meeting of the Modularity Working Group
=
Meeting started by nils at 15:01:00 UTC.
Minutes:
https://bugzilla.redhat.com/show_bug.cgi?id=1011333
Jitka Plesnikova changed:
What|Removed |Added
Version|27 |28
--- Comment #12 from Jitka
On Tue, Nov 27, 2018 at 11:05 AM Josh Boyer wrote:
> On Tue, Nov 27, 2018 at 10:13 AM Owen Taylor wrote:
> > But for the next thousand or so Fedora developers, the release cycle
> > is actually not a big deal - not something that takes much of their
> > time - and it gives them a regular place
https://bugzilla.redhat.com/show_bug.cgi?id=1007199
Jitka Plesnikova changed:
What|Removed |Added
Version|27 |28
--- Comment #12 from Jitka
https://bugzilla.redhat.com/show_bug.cgi?id=987118
Jitka Plesnikova changed:
What|Removed |Added
Version|27 |28
--- Comment #9 from Jitka
https://bugzilla.redhat.com/show_bug.cgi?id=1206915
Jitka Plesnikova changed:
What|Removed |Added
Version|27 |28
--
You are receiving this
On Tue, Nov 27, 2018 at 10:13 AM Owen Taylor wrote:
>
> On Mon, Nov 26, 2018 at 9:26 PM Brendan Conoboy wrote:>
> > On 11/16/18 7:50 AM, Paul Frields wrote:
> > [snip]
> > > We should skip the F31 release cycle and leave F30 in place longer in
> > > order to focus on improving the tooling and
https://bugzilla.redhat.com/show_bug.cgi?id=1377997
--- Comment #6 from Ben Cotton ---
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30 Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from
That's exactly question I had in mind, thanks for bringing it up!
Personally, if we won't be able to push breaking changes in F30, then
after some time people will not be happy about outdated software and
will leave distribution I think.
For maintainers it would probably mean that F29 won't get
https://bugzilla.redhat.com/show_bug.cgi?id=1450364
--- Comment #3 from Ben Cotton ---
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30 Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from
https://bugzilla.redhat.com/show_bug.cgi?id=1379554
--- Comment #6 from Ben Cotton ---
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30 Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from
https://bugzilla.redhat.com/show_bug.cgi?id=987118
--- Comment #8 from Ben Cotton ---
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30 Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from
https://bugzilla.redhat.com/show_bug.cgi?id=1011333
--- Comment #11 from Ben Cotton ---
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30 Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from
https://bugzilla.redhat.com/show_bug.cgi?id=1206915
--- Comment #10 from Ben Cotton ---
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30 Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from
https://bugzilla.redhat.com/show_bug.cgi?id=1007199
--- Comment #11 from Ben Cotton ---
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30 Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from
On Tue, Nov 27, 2018 at 10:40 AM Owen Taylor wrote:
>
> One of the key parts of making a decision to delay/skip F31 is
> figuring out, ahead of the decision, what the expected experience is
> for users and packagers. Does F30 have normal stability, or do we try
> to keep users happy by moving
OLD: Fedora-Rawhide-20181126.n.0
NEW: Fedora-Rawhide-20181127.n.0
= SUMMARY =
Added images:0
Dropped images: 0
Added packages: 10
Dropped packages:1
Upgraded packages: 116
Downgraded packages: 0
Size of added packages: 56.01 MiB
Size of dropped packages
https://bugzilla.redhat.com/show_bug.cgi?id=1646135
Jitka Plesnikova changed:
What|Removed |Added
Status|ON_QA |CLOSED
Resolution|---
https://bugzilla.redhat.com/show_bug.cgi?id=1612474
Jitka Plesnikova changed:
What|Removed |Added
Status|ON_QA |CLOSED
Resolution|---
One of the key parts of making a decision to delay/skip F31 is
figuring out, ahead of the decision, what the expected experience is
for users and packagers. Does F30 have normal stability, or do we try
to keep users happy by moving things forward with ad-hoc updates and
cross-our-fingers and hope
https://bugzilla.redhat.com/show_bug.cgi?id=1581851
Jitka Plesnikova changed:
What|Removed |Added
Status|ON_QA |CLOSED
CC|
https://bugzilla.redhat.com/show_bug.cgi?id=1584611
Jitka Plesnikova changed:
What|Removed |Added
Status|ON_QA |CLOSED
CC|
https://bugzilla.redhat.com/show_bug.cgi?id=1231244
--- Comment #7 from Ben Cotton ---
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30 Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from
https://bugzilla.redhat.com/show_bug.cgi?id=1456772
--- Comment #4 from Ben Cotton ---
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30 Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from
On Tue, Nov 27, 2018 at 10:12 AM Stephen John Smoogen wrote:
> Define what a compose is? Currently it is a word which covers a
> multitude of different processes and reasons for those processes. We
> can't 'fix' or even 'replace' or parallel them without actually
> knowing why someone duct taped
https://bugzilla.redhat.com/show_bug.cgi?id=1581851
--- Comment #8 from Ben Cotton ---
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30 Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from
On Mon, Nov 26, 2018 at 9:26 PM Brendan Conoboy wrote:>
> On 11/16/18 7:50 AM, Paul Frields wrote:
> [snip]
> > We should skip the F31 release cycle and leave F30 in place longer in
> > order to focus on improving the tooling and testing changes. These
> > tooling changes will improve the overall
On Tue, 27 Nov 2018 at 09:59, Owen Taylor wrote:
>
> A lot of discussion about improving the compose process seem to end up
> with a "reality check" - that ideas have already been tried but don't
> work because of requirements a) b) c) d). You can't have the pony, but
> maybe if a lot of effort
https://bugzilla.redhat.com/show_bug.cgi?id=1399506
Jitka Plesnikova changed:
What|Removed |Added
Version|27 |28
--
You are receiving this
https://bugzilla.redhat.com/show_bug.cgi?id=1584611
--- Comment #9 from Ben Cotton ---
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30 Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from
https://bugzilla.redhat.com/show_bug.cgi?id=1600504
Petr Pisar changed:
What|Removed |Added
Version|27 |28
--
You are receiving this mail
https://bugzilla.redhat.com/show_bug.cgi?id=1473368
Jitka Plesnikova changed:
What|Removed |Added
Version|27 |28
--
You are receiving this
https://bugzilla.redhat.com/show_bug.cgi?id=1462394
Pavel Raiskup changed:
What|Removed |Added
Keywords||FutureFeature
Status|NEW
https://bugzilla.redhat.com/show_bug.cgi?id=1600504
--- Comment #1 from Ben Cotton ---
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30 Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from
A lot of discussion about improving the compose process seem to end up
with a "reality check" - that ideas have already been tried but don't
work because of requirements a) b) c) d). You can't have the pony, but
maybe if a lot of effort is put into it, you can have a faster rocking
horse.
If want
On Tue, Nov 27, 2018 at 8:21 AM Justin Forbes wrote:
>
> Long cycles have been done before, and will be done again, it has been
> 4 or 5 years since the last one. I think skipping to a yearly cadence
> for every release isn't such a great idea. There are benefits to the
> cadence we have, but I
https://bugzilla.redhat.com/show_bug.cgi?id=1399506
--- Comment #5 from Ben Cotton ---
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30 Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from
https://bugzilla.redhat.com/show_bug.cgi?id=1462394
--- Comment #4 from Ben Cotton ---
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30 Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from
1 - 100 of 138 matches
Mail list logo
