Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2019-01-06 Thread Matthew Miller
On Sun, Jan 06, 2019 at 12:35:25PM -0500, Paul Frields wrote: > Update: We'll be having discussions over the next few weeks to figure > out how we can accommodate Lifecycle work without interrupting the > Fedora release cadence. That includes in Brno, where we can meet up > f2f with people working

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2019-01-06 Thread Paul Frields
Update: We'll be having discussions over the next few weeks to figure out how we can accommodate Lifecycle work without interrupting the Fedora release cadence. That includes in Brno, where we can meet up f2f with people working on parallel projects in automation, CI, and so on. We may also be

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-28 Thread Randy Barlow
On Wed, 2018-11-28 at 18:19 +0100, Kevin Kofler wrote: > And why do we need to stop the presses to do that? This is entirely > orthogonal to distribution development and can be done in parallel. The problem is that the people who do the work to get the release done are the same people who would

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-28 Thread Kevin Kofler
Matthew Miller wrote: > I know it was a big time-off holiday week in the US, but I expected a > little more interest in this post. Perhaps it seemed like too much text to > digest along with turkey and stuffing. :) I'm highlighting it with a > subject reflecting the big, direct impact, and here's

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-27 Thread Adam Williamson
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

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-27 Thread Peter Robinson
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

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-27 Thread Randy Barlow
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

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-27 Thread Paul Frields
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

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-27 Thread Dennis Gilmore
El lun, 26-11-2018 a las 19:44 -0500, Paul Frields escribió: > On Mon, Nov 26, 2018 at 5:47 PM Dennis Gilmore > wrote: > > El lun, 26-11-2018 a las 17:14 -0500, Josh Boyer escribió: > > > Because the people that would be tasked with doing the > > > development are > > > also tasked with cranking

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-27 Thread Neal Gompa
On Tue, Nov 27, 2018 at 9:08 AM John Florian wrote: > > On 11/26/18 3:53 PM, Kevin Fenzi wrote: > > The one issue I see off hand is that koji > > tags are kind of expensive so we can't just tag everything the way we > > may want > > Can you please elaborate a bit on this? What makes them

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-27 Thread John Florian
On 11/26/18 3:53 PM, Kevin Fenzi wrote: The one issue I see off hand is that koji tags are kind of expensive so we can't just tag everything the way we may want Can you please elaborate a bit on this?  What makes them expensive? ___ devel mailing

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-27 Thread Paul Frields
On Tue, Nov 27, 2018 at 4:41 AM Miroslav Suchý wrote: > > Dne 26. 11. 18 v 17:03 Matthew Miller napsal(a): > > * embrace Taiga (an open source kanban tool) for project planning > > * fix the compose speed (target: one hour!) > > * really actually for real gated Rawhide > > * better CI pipeline

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-27 Thread Josh Boyer
On Mon, Nov 26, 2018 at 7:45 PM Paul Frields wrote: > > On Mon, Nov 26, 2018 at 5:47 PM Dennis Gilmore wrote: > > El lun, 26-11-2018 a las 17:14 -0500, Josh Boyer escribió: > > > Because the people that would be tasked with doing the development are > > > also tasked with cranking out the

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-27 Thread Vít Ondruch
Dne 26. 11. 18 v 20:01 Randy Barlow napsal(a): > On Mon, 2018-11-26 at 17:23 +0100, Igor Gnatenko wrote: >>> * really actually for real gated Rawhide >> Is the "creating side tag for chain builds or by automated requests" >> is planned here? >> When I deal with rust packages, I often need to

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-27 Thread Miroslav Suchý
Dne 26. 11. 18 v 17:03 Matthew Miller napsal(a): > * embrace Taiga (an open source kanban tool) for project planning > * fix the compose speed (target: one hour!) > * really actually for real gated Rawhide > * better CI pipeline tests for everything > * define a base platform -- Red Hat wants to

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread drago01
On Monday, November 26, 2018, Matthew Miller wrote: > On Fri, Nov 16, 2018 at 09:50:33AM -0500, Paul Frields wrote: > > Here's the summary from the page, which proposes we pause the release > > after F30 for these efforts: > > I know it was a big time-off holiday week in the US, but I expected a

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Paul Frields
On Mon, Nov 26, 2018 at 5:47 PM Dennis Gilmore wrote: > El lun, 26-11-2018 a las 17:14 -0500, Josh Boyer escribió: > > Because the people that would be tasked with doing the development are > > also tasked with cranking out the release. It's a "need more people > > problem". > > This is no

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Dennis Gilmore
El lun, 26-11-2018 a las 17:14 -0500, Josh Boyer escribió: > On Mon, Nov 26, 2018 at 5:01 PM Peter Robinson > wrote: > > On Mon, Nov 26, 2018 at 9:48 PM Matthew Miller < > > mat...@fedoraproject.org> wrote: > > > On Mon, Nov 26, 2018 at 08:02:26PM +, Peter Robinson wrote: > > > > transactions

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Josh Boyer
On Mon, Nov 26, 2018 at 5:01 PM Peter Robinson wrote: > > On Mon, Nov 26, 2018 at 9:48 PM Matthew Miller > wrote: > > > > On Mon, Nov 26, 2018 at 08:02:26PM +, Peter Robinson wrote: > > > transactions is substantial. This may solve (or greatly reduce) the > > > compose speed problem, TBD."

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Peter Robinson
On Mon, Nov 26, 2018 at 9:48 PM Matthew Miller wrote: > > On Mon, Nov 26, 2018 at 08:02:26PM +, Peter Robinson wrote: > > transactions is substantial. This may solve (or greatly reduce) the > > compose speed problem, TBD." but it doesn't report the context of the > > "speed increase for

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Matthew Miller
On Mon, Nov 26, 2018 at 08:02:26PM +, Peter Robinson wrote: > transactions is substantial. This may solve (or greatly reduce) the > compose speed problem, TBD." but it doesn't report the context of the > "speed increase for transactions" like which transactions? > There's a lot of I/O

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Igor Gnatenko
On Mon, Nov 26, 2018, 20:09 Randy Barlow On Mon, 2018-11-26 at 17:23 +0100, Igor Gnatenko wrote: > > > * really actually for real gated Rawhide > > > > Is the "creating side tag for chain builds or by automated requests" > > is planned here? > > When I deal with rust packages, I often need to

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Kevin Fenzi
On 11/26/18 11:55 AM, Paul Frields wrote: > On Mon, Nov 26, 2018 at 2:42 PM Adam Williamson >> >> While we're on the topic of unicorns, if I were the person actually in >> charge of this and had the freedom to do it how I wanted, what I'd >> really want to do is create a much more *modular*

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Stephen Gallagher
On Mon, Nov 26, 2018 at 3:34 PM Peter Robinson wrote: > > On Mon, Nov 26, 2018 at 8:22 PM Stephen Gallagher wrote: > > > > On Mon, Nov 26, 2018 at 3:03 PM Peter Robinson wrote: > > > There's no facts or details, to quote "The reported speed increase for > > > transactions is substantial. This

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Peter Robinson
On Mon, Nov 26, 2018 at 8:22 PM Stephen Gallagher wrote: > > On Mon, Nov 26, 2018 at 3:03 PM Peter Robinson wrote: > > There's no facts or details, to quote "The reported speed increase for > > transactions is substantial. This may solve (or greatly reduce) the > > compose speed problem, TBD."

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Stephen Gallagher
On Mon, Nov 26, 2018 at 3:03 PM Peter Robinson wrote: > There's no facts or details, to quote "The reported speed increase for > transactions is substantial. This may solve (or greatly reduce) the > compose speed problem, TBD." but it doesn't report the context of the > "speed increase for

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Peter Robinson
On Mon, Nov 26, 2018 at 7:52 PM Paul Frields wrote: > > On Mon, Nov 26, 2018 at 1:59 PM 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

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Matthew Miller
On Mon, Nov 26, 2018 at 11:39:52AM -0800, Adam Williamson wrote: > While we're on the topic of unicorns, if I were the person actually in > charge of this and had the freedom to do it how I wanted, what I'd > really want to do is create a much more *modular* compose process, > where inputs and

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Paul Frields
On Mon, Nov 26, 2018 at 2:42 PM Adam Williamson wrote: > On Mon, 2018-11-26 at 11:30 -0800, Kevin Fenzi wrote: > > Yeah, I think our goal should be 1 minute... just as realistic as one > > hour. ;) > > > > I have not looked into things recently. However: > > > > * The mock fsync change

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Paul Frields
On Mon, Nov 26, 2018 at 1:59 PM 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 > > > wrote: > > > > On Fri, Nov 16, 2018 at 09:50:33AM -0500,

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Mohan Boddu
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: > >

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Peter Robinson
On Mon, Nov 26, 2018 at 7:47 PM Mohan Boddu wrote: > > > > 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:

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Peter Robinson
On Mon, Nov 26, 2018 at 7: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: > >

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Mohan Boddu
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 < >

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Adam Williamson
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: > > > > On Mon, Nov 26, 2018 at 4:05 PM Matthew Miller > > > > wrote:

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Kevin Fenzi
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 >>> wrote: On Fri, Nov 16, 2018 at 09:50:33AM -0500, Paul Frields wrote:

Re: Release Cadence WAS: Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Kevin Fenzi
On 11/26/18 8:21 AM, Brian (bex) Exelbierd wrote: > On Mon, Nov 26, 2018 at 5:05 PM Matthew Miller > wrote: >> >> On Fri, Nov 16, 2018 at 09:50:33AM -0500, Paul Frields wrote: >>> Here's the summary from the page, which proposes we pause the release >>> after F30 for these efforts: >> >> I know

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Adam Williamson
On Mon, 2018-11-26 at 20:03 +0100, Fabio Valentini wrote: > > Also, I find it funny that - somehow - tons of resources would be > available for "better CI pipeline tests for everything" (!), but we'd > have to "focus resources" when it comes to the fedora "platform" > itself. These two sort of

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Fabio Valentini
On Mon, Nov 26, 2018 at 5:05 PM Matthew Miller wrote: > > On Fri, Nov 16, 2018 at 09:50:33AM -0500, Paul Frields wrote: > > Here's the summary from the page, which proposes we pause the release > > after F30 for these efforts: > > I know it was a big time-off holiday week in the US, but I

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Randy Barlow
On Mon, 2018-11-26 at 17:23 +0100, Igor Gnatenko wrote: > > * really actually for real gated Rawhide > > Is the "creating side tag for chain builds or by automated requests" > is planned here? > When I deal with rust packages, I often need to build some update > which will break other packages

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Peter Robinson
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 > > wrote: > > > On Fri, Nov 16, 2018 at 09:50:33AM -0500, Paul Frields wrote: > > > > Here's the summary from the page, which

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Adam Williamson
On Mon, 2018-11-26 at 18:44 +, Peter Robinson wrote: > On Mon, Nov 26, 2018 at 4:05 PM Matthew Miller > wrote: > > On Fri, Nov 16, 2018 at 09:50:33AM -0500, Paul Frields wrote: > > > Here's the summary from the page, which proposes we pause the release > > > after F30 for these efforts: > >

Re: Release Cadence WAS: Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Peter Robinson
On Mon, Nov 26, 2018 at 4:23 PM Brian (bex) Exelbierd wrote: > > On Mon, Nov 26, 2018 at 5:05 PM Matthew Miller > wrote: > > > > On Fri, Nov 16, 2018 at 09:50:33AM -0500, Paul Frields wrote: > > > Here's the summary from the page, which proposes we pause the release > > > after F30 for these

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Peter Robinson
On Mon, Nov 26, 2018 at 4:05 PM Matthew Miller wrote: > > On Fri, Nov 16, 2018 at 09:50:33AM -0500, Paul Frields wrote: > > Here's the summary from the page, which proposes we pause the release > > after F30 for these efforts: > > I know it was a big time-off holiday week in the US, but I

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread mcatanzaro
On Mon, Nov 26, 2018 at 10:03 AM, Matthew Miller wrote: I know it was a big time-off holiday week in the US, but I expected a little more interest in this post. Perhaps it seemed like too much text to digest along with turkey and stuffing. :) I'm highlighting it with a subject reflecting the

Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Igor Gnatenko
On Mon, Nov 26, 2018 at 5:14 PM Matthew Miller wrote: > > On Fri, Nov 16, 2018 at 09:50:33AM -0500, Paul Frields wrote: > > Here's the summary from the page, which proposes we pause the release > > after F30 for these efforts: > > I know it was a big time-off holiday week in the US, but I

Release Cadence WAS: Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Brian (bex) Exelbierd
On Mon, Nov 26, 2018 at 5:05 PM Matthew Miller wrote: > > On Fri, Nov 16, 2018 at 09:50:33AM -0500, Paul Frields wrote: > > Here's the summary from the page, which proposes we pause the release > > after F30 for these efforts: > > I know it was a big time-off holiday week in the US, but I

Proposal: delay F31 release to work out infrastructure and lifecycle challenges

2018-11-26 Thread Matthew Miller
On Fri, Nov 16, 2018 at 09:50:33AM -0500, Paul Frields wrote: > Here's the summary from the page, which proposes we pause the release > after F30 for these efforts: I know it was a big time-off holiday week in the US, but I expected a little more interest in this post. Perhaps it seemed like too