Re: Add a rule to have a compose when Fedora branched

Release Engineering issue is created and change is proposed. Thanks everyone a lot for your help with the change and with finding the best solution! Jirka On Wed, 2019-11-13 at 12:40 -0800, Kevin Fenzi wrote: > On Wed, Nov 13, 2019 at 02:59:56PM +0100, jkone...@redhat.com wrote: > > On Wed,

Re: Add a rule to have a compose when Fedora branched

On Wed, Nov 13, 2019 at 02:59:56PM +0100, jkone...@redhat.com wrote: > On Wed, 2019-11-13 at 14:49 +0100, Miro Hrončok wrote: > > On 13. 11. 19 14:12, jkone...@redhat.com wrote: > > > Here's the draft. It would be great if you can check it out and do > > > the > > > appropriate edits to improve

Re: Add a rule to have a compose when Fedora branched

On Wed, 2019-11-13 at 15:04 +0100, Miro Hrončok wrote: > On 13. 11. 19 14:59, jkone...@redhat.com wrote: > > Link to this thread is at the bottom of the proposal in the > > Documentation section. > > oh, sorry for not noticing that. > No problem at all. Thanks a lot for your polishing!

Re: Add a rule to have a compose when Fedora branched

On 13. 11. 19 14:59, jkone...@redhat.com wrote: Link to this thread is at the bottom of the proposal in the Documentation section. oh, sorry for not noticing that. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list --

Re: Add a rule to have a compose when Fedora branched

On Wed, 2019-11-13 at 14:49 +0100, Miro Hrončok wrote: > On 13. 11. 19 14:12, jkone...@redhat.com wrote: > > Here's the draft. It would be great if you can check it out and do > > the > > appropriate edits to improve the Change. > > > >

Re: Add a rule to have a compose when Fedora branched

On 13. 11. 19 14:12, jkone...@redhat.com wrote: Here's the draft. It would be great if you can check it out and do the appropriate edits to improve the Change. https://fedoraproject.org/wiki/Changes/Freeze_after_branching_until_compose_is_ready I've made minor adjustments. What is missing:

Re: Add a rule to have a compose when Fedora branched

Here's the draft. It would be great if you can check it out and do the appropriate edits to improve the Change. https://fedoraproject.org/wiki/Changes/Freeze_after_branching_until_compose_is_ready Thanks Miro! Jirka On Mon, 2019-11-11 at 19:16 +0100, Miro Hrončok wrote: > On 11. 11. 19 19:09,

Re: Add a rule to have a compose when Fedora branched

If you think the change proposal is a better way then I'll create a draft and before sending it I'll contact you off the list to polish it. Thanks a lot everyone for helping. You are the best! Jirka On Mon, 2019-11-11 at 19:16 +0100, Miro Hrončok wrote: > On 11. 11. 19 19:09, Miro Hrončok

Re: Add a rule to have a compose when Fedora branched

On 11. 11. 19 19:09, Miro Hrončok wrote: Excellent. I think this is ready to be presented to fesco for a vote. Unless we decide it requires a change proposal. To limit the required bureaucracy, I can help draft it. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

Re: Add a rule to have a compose when Fedora branched

On 11. 11. 19 18:23, Kevin Fenzi wrote: On Mon, Nov 11, 2019 at 09:51:33AM -0500, Ben Cotton wrote: On Mon, Nov 11, 2019 at 4:01 AM Miro Hrončok wrote: Before you do this, can we figure out the details? 1. Do we use bodhi to handle the freeze? Previously, this would not be possible, as

Re: Add a rule to have a compose when Fedora branched

On Mon, Nov 11, 2019 at 09:51:33AM -0500, Ben Cotton wrote: > On Mon, Nov 11, 2019 at 4:01 AM Miro Hrončok wrote: > > > > Before you do this, can we figure out the details? > > > > 1. Do we use bodhi to handle the freeze? > > > > Previously, this would not be possible, as bodhi was not yet

Re: Add a rule to have a compose when Fedora branched

On Mon, Nov 11, 2019 at 4:01 AM Miro Hrončok wrote: > > Before you do this, can we figure out the details? > > 1. Do we use bodhi to handle the freeze? > > Previously, this would not be possible, as bodhi was not yet "activated" at > branching, however with rawhide gating (and hopefully "branched

Re: Add a rule to have a compose when Fedora branched

On 11. 11. 19 8:06, jkone...@redhat.com wrote: On Fri, 2019-11-08 at 12:16 -0500, Ben Cotton wrote: On Fri, Nov 8, 2019 at 11:54 AM wrote: I agree with you in general but I don't like the `brief` wording here. What that means exactly? I would rather go with specifying a strong freeze. Meaning

Re: Add a rule to have a compose when Fedora branched

On Fri, 2019-11-08 at 12:16 -0500, Ben Cotton wrote: > On Fri, Nov 8, 2019 at 11:54 AM wrote: > > I agree with you in general but I don't like the `brief` wording > > here. > > What that means exactly? > > I would rather go with specifying a strong freeze. Meaning that the > > freeze will

Re: Add a rule to have a compose when Fedora branched

On Fri, Nov 8, 2019 at 11:54 AM wrote: > > I agree with you in general but I don't like the `brief` wording here. > What that means exactly? > I would rather go with specifying a strong freeze. Meaning that the > freeze will continue until compose is available. > By "brief" I mean "only as long

Re: Add a rule to have a compose when Fedora branched

On Fri, 2019-11-08 at 07:20 -0800, Kevin Fenzi wrote: > On Thu, Nov 07, 2019 at 08:43:44PM +0100, Miro Hrončok wrote: > > On 07. 11. 19 18:35, Ben Cotton wrote: > > > Here's the link to the Community Blog post that looks at the > > > schedule options: > > >

Re: Add a rule to have a compose when Fedora branched

On Thu, Nov 07, 2019 at 08:43:44PM +0100, Miro Hrončok wrote: > On 07. 11. 19 18:35, Ben Cotton wrote: > > Here's the link to the Community Blog post that looks at the schedule > > options: > > https://communityblog.fedoraproject.org/accommodating-flock-in-the-release-schedule/ > > From the

Re: Add a rule to have a compose when Fedora branched

On 07. 11. 19 18:35, Ben Cotton wrote: Here's the link to the Community Blog post that looks at the schedule options: https://communityblog.fedoraproject.org/accommodating-flock-in-the-release-schedule/ From the post: I’m inclined to go with option 0, plus a brief freeze after branch. This

Re: Add a rule to have a compose when Fedora branched

Here's the link to the Community Blog post that looks at the schedule options: https://communityblog.fedoraproject.org/accommodating-flock-in-the-release-schedule/ I have disabled comments on that post so that we can keep the conversation on this thread. -- Ben Cotton He / Him / His Fedora

Re: Add a rule to have a compose when Fedora branched

On Mon, Nov 4, 2019 at 8:13 AM wrote: > > Could you please tell us if the post is published yet? And if so, could > you please share the link? > It is not. It will publish on Thursday. I'll share the link here when it goes up. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat

Re: Add a rule to have a compose when Fedora branched

Hi Kevin, Could we please create an action item list for FESCO ticket? I guess at the end we don't want to freeze Rawhide but we should have steps required for the branched Fedora freeze. Do you know how to do that or could you point someone here please? Jirka On Sun, 2019-09-22 at 10:48

Re: Add a rule to have a compose when Fedora branched

On Mon, 2019-10-28 at 14:29 -0400, Ben Cotton wrote: > On Mon, Oct 28, 2019 at 1:43 PM Kevin Fenzi wrote: > > On Tue, Oct 22, 2019 at 02:09:04PM +0200, jkone...@redhat.com > > wrote: > > > I guess it will be easier to just think about the branching date > > > when > > > Flock schedule is

Re: Add a rule to have a compose when Fedora branched

On Tue, Oct 29, 2019 at 02:03:03PM +0100, jkone...@redhat.com wrote: > > As far as I remember this problem is not new. It just got really > problematic on F31. However, I remember that almost every release we > have a gab between the branching and compose creation. Most of the time > it's not

Re: Add a rule to have a compose when Fedora branched

On Mon, 2019-10-28 at 14:29 -0400, Ben Cotton wrote: > On Mon, Oct 28, 2019 at 1:43 PM Kevin Fenzi wrote: > > On Tue, Oct 22, 2019 at 02:09:04PM +0200, jkone...@redhat.com > > wrote: > > > I guess it will be easier to just think about the branching date > > > when > > > Flock schedule is

Re: Add a rule to have a compose when Fedora branched

On Mon, Oct 28, 2019 at 1:43 PM Kevin Fenzi wrote: > > On Tue, Oct 22, 2019 at 02:09:04PM +0200, jkone...@redhat.com wrote: > > > > I guess it will be easier to just think about the branching date when > > Flock schedule is creating. However, I'm not familiar with the > > scheduling so I'm

Re: Add a rule to have a compose when Fedora branched

On Tue, Oct 22, 2019 at 02:09:04PM +0200, jkone...@redhat.com wrote: > > I guess it will be easier to just think about the branching date when > Flock schedule is creating. However, I'm not familiar with the > scheduling so I'm probably not the right person who should answer this. Perhaps Ben

Re: Add a rule to have a compose when Fedora branched

On Mon, 2019-10-21 at 11:19 -0700, Kevin Fenzi wrote: > On Mon, Oct 14, 2019 at 11:59:30AM +0200, jkone...@redhat.com wrote: > > FYI: FESCO ticket was created > > > > https://pagure.io/fesco/issue/2246 > > Yeah, and we had a bit more discussion there, which we probibly > should > have just had

Re: Add a rule to have a compose when Fedora branched

On Mon, Oct 14, 2019 at 11:59:30AM +0200, jkone...@redhat.com wrote: > FYI: FESCO ticket was created > > https://pagure.io/fesco/issue/2246 Yeah, and we had a bit more discussion there, which we probibly should have just had here. ;) In particular bcotton asked how we avoid scheduling the

Re: Add a rule to have a compose when Fedora branched

FYI: FESCO ticket was created https://pagure.io/fesco/issue/2246 On Tue, 2019-09-17 at 15:58 +0200, jkone...@redhat.com wrote: > Hello everyone, > > I'm Anaconda developer and I'm also taking care about our > infrastructure and this Fedora release brought me a plenty of > "unnecessary" work

Re: Add a rule to have a compose when Fedora branched

On Sat, Sep 21, 2019 at 11:04:29PM +0200, Pavel Raiskup wrote: > On Friday, September 20, 2019 6:08:46 PM CEST Kevin Fenzi wrote: > > On 9/20/19 4:39 AM, jkone...@redhat.com wrote: > > > What COPR was doing (I think they changed it after F31) then before a > > > new chroot in COPR appeared they

Re: Add a rule to have a compose when Fedora branched

On 22. 09. 19 1:07, Neal Gompa wrote: ok. That does give developers 2 less weeks to finish up any changes (or get FE/blockers for them), but we could do that, sure. What does everyone else think? I'm not really in favor of any more time compressions in the schedule than we already have. It's

Re: Add a rule to have a compose when Fedora branched

On Fri, Sep 20, 2019 at 12:19 PM Kevin Fenzi wrote: > > On 9/19/19 3:33 PM, Miro Hrončok wrote: > > On 19. 09. 19 23:29, Kevin Fenzi wrote: > * Stop rawhide composes until we have a branched compose. This may > not > be needed with the change to make rawhide use 'rawhide' and not

Re: Add a rule to have a compose when Fedora branched

On Friday, September 20, 2019 6:08:46 PM CEST Kevin Fenzi wrote: > On 9/20/19 4:39 AM, jkone...@redhat.com wrote: > > What COPR was doing (I think they changed it after F31) then before a > > new chroot in COPR appeared they copied the latest Rawhide chroot to > > have something working in the new

Re: Add a rule to have a compose when Fedora branched

On 9/19/19 3:33 PM, Miro Hrončok wrote: > On 19. 09. 19 23:29, Kevin Fenzi wrote: * Stop rawhide composes until we have a branched compose. This may not be needed with the change to make rawhide use 'rawhide' and not the number, but we should consider it if we don't have a

Re: Add a rule to have a compose when Fedora branched

On 9/20/19 4:39 AM, jkone...@redhat.com wrote: > On Thu, 2019-09-19 at 14:29 -0700, Kevin Fenzi wrote: >> On 9/18/19 1:41 AM, jkone...@redhat.com wrote: ...snip... >>> In my F31 case most importantly copr will be in similar situation >>> that >>> they will use Rawhide *new* compose (if they

Re: Add a rule to have a compose when Fedora branched

On Thu, 2019-09-19 at 14:29 -0700, Kevin Fenzi wrote: > On 9/18/19 1:41 AM, jkone...@redhat.com wrote: > > Hi Kevin, > > Thanks for the explanation. See my comments below. > > ...snip... > > > > * Stop rawhide composes until we have a branched compose. This > > > may > > > not > > > be needed

Re: Add a rule to have a compose when Fedora branched

On 19. 09. 19 23:29, Kevin Fenzi wrote: * Stop rawhide composes until we have a branched compose. This may not be needed with the change to make rawhide use 'rawhide' and not the number, but we should consider it if we don't have a compose to avoid confusion. Where should I signed this?:) But

Re: Add a rule to have a compose when Fedora branched

On 9/18/19 1:41 AM, jkone...@redhat.com wrote: > Hi Kevin, > Thanks for the explanation. See my comments below. ...snip... >> * Stop rawhide composes until we have a branched compose. This may >> not >> be needed with the change to make rawhide use 'rawhide' and not the >> number, but we should

Re: Add a rule to have a compose when Fedora branched

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 >

Re: Add a rule to have a compose when Fedora branched

On 9/18/19 12:02 AM, Miroslav Suchý wrote: > Dne 17. 09. 19 v 18:28 Kevin Fenzi napsal(a): >> Branching is not just "oh, make a new compose". There's a ton of >> steps/work that happens then, including: >> >> * Making a new branch on all active rpms >> * Switching to a new signing key in rawhide.

Re: Add a rule to have a compose when Fedora branched

Hi Kevin, Thanks for the explanation. See my comments below. On Tue, 2019-09-17 at 09:28 -0700, 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 > > >

Re: Add a rule to have a compose when Fedora branched

Dne 17. 09. 19 v 18:28 Kevin Fenzi napsal(a): Branching is not just "oh, make a new compose". There's a ton of steps/work that happens then, including: * Making a new branch on all active rpms * Switching to a new signing key in rawhide. * New pungi-fedora config, new comps, new kickstarts. *

Re: Add a rule to have a compose when Fedora branched

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 >> asking for is to have a base ground which is not available

Re: Add a rule to have a compose when Fedora branched

- Original Message - > From: "Ben Cotton" > To: "Development discussions related to Fedora" > > Sent: Tuesday, September 17, 2019 4:38:50 PM > Subject: Re: Add a rule to have a compose when Fedora branched > > On Tue, Sep 17, 2019 at 10:00 AM wrote: > > > > I want to ask for an

Re: Add a rule to have a compose when Fedora branched

- Original Message - > From: "Miro Hrončok" > To: devel@lists.fedoraproject.org > Cc: "Mohan Boddu" , "Lubomir Sedlar" , > "Kevin Fenzi" > Sent: Tuesday, September 17, 2019 5:04:10 PM > Subject: Re: Add a rule to have a compose when Fedora branched > > On 17. 09. 19 17:00,

Re: Add a rule to have a compose when Fedora branched

On Tue, 2019-09-17 at 10:38 -0400, Ben Cotton wrote: > On Tue, Sep 17, 2019 at 10:00 AM wrote: > > I want to ask for an improvement here. Ideal solution for me would > > be > > to add rule that there have to be compose to do the branching and > > if > > the compose fails then the branching won't

Re: Add a rule to have a compose when Fedora branched

On 17. 09. 19 17:15, jkone...@redhat.com wrote: Interesting they don't use any linters or just using different one? Don't you know? I usually use flake8 and black. However only upstream, installed via pip via tox. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

Re: Add a rule to have a compose when Fedora branched

On Tue, 2019-09-17 at 16:56 +0200, Miro Hrončok wrote: > On 17. 09. 19 16:39, jkone...@redhat.com wrote: > > Hi Miro, > > > > No, I did not wanted to tell that the python 3.8 transition was > > badly > > executed. The problem was more about timing. > > > > I was fighting with Fedora 31 and we

Re: Add a rule to have a compose when Fedora branched

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 asking for is to have a base ground which is not available right now. That is actually a nice proposal. I

Re: Add a rule to have a compose when Fedora branched

On Tue, 2019-09-17 at 16:31 +0200, Miro Hrončok wrote: > On 17. 09. 19 15:58, jkone...@redhat.com wrote: > > I want to ask for an improvement here. Ideal solution for me would > > be > > to add rule that there have to be compose to do the branching and > > if > > the compose fails then the

Re: Add a rule to have a compose when Fedora branched

On 17. 09. 19 16:39, jkone...@redhat.com wrote: Hi Miro, No, I did not wanted to tell that the python 3.8 transition was badly executed. The problem was more about timing. I was fighting with Fedora 31 and we had Rawhide as replacement for F31 tests because the environment is usually not that

Re: Add a rule to have a compose when Fedora branched

On Tue, 2019-09-17 at 16:33 +0200, Fabio Valentini wrote: > On Tue, Sep 17, 2019, 16:28 Miro Hrončok wrote: > > On 17. 09. 19 15:58, jkone...@redhat.com wrote: > > > > > To make things even worse there was a switch to python 3.8 on > > Rawhide > > > > > which wasn't really prepared (pylint did

Re: Add a rule to have a compose when Fedora branched

On 17. 09. 19 16:33, Fabio Valentini wrote: On Tue, Sep 17, 2019, 16:28 Miro Hrončok > wrote: On 17. 09. 19 15:58, jkone...@redhat.com wrote: > To make things even worse there was a switch to python 3.8 on Rawhide > which

Re: Add a rule to have a compose when Fedora branched

Hi Miro, No, I did not wanted to tell that the python 3.8 transition was badly executed. The problem was more about timing. I was fighting with Fedora 31 and we had Rawhide as replacement for F31 tests because the environment is usually not that different. However, when the switch to python 3.8

Re: Add a rule to have a compose when Fedora branched

On Tue, Sep 17, 2019 at 10:00 AM wrote: > > I want to ask for an improvement here. Ideal solution for me would be > to add rule that there have to be compose to do the branching and if > the compose fails then the branching won't happen. Not sure if this is > doable or how hard it would be to

Re: Add a rule to have a compose when Fedora branched

On Tue, Sep 17, 2019, 16:28 Miro Hrončok wrote: > On 17. 09. 19 15:58, jkone...@redhat.com wrote: > > To make things even worse there was a switch to python 3.8 on Rawhide > > which wasn't really prepared (pylint did not worked). > > I trust that your intentions were only the best when you wrote

Re: Add a rule to have a compose when Fedora branched

On 17. 09. 19 15:58, jkone...@redhat.com wrote: I want to ask for an improvement here. Ideal solution for me would be to add rule that there have to be compose to do the branching and if the compose fails then the branching won't happen. We need to branch before we do the branched compose.

Re: Add a rule to have a compose when Fedora branched

On 17. 09. 19 15:58, jkone...@redhat.com wrote: To make things even worse there was a switch to python 3.8 on Rawhide which wasn't really prepared (pylint did not worked). I trust that your intentions were only the best when you wrote your e-mail, but this statement kinda surprises me. The

Add a rule to have a compose when Fedora branched

Hello everyone, I'm Anaconda developer and I'm also taking care about our infrastructure and this Fedora release brought me a plenty of "unnecessary" work thanks to the fact that compose for Fedora 31 was not available until a week before beta freeze. That is too late. I wasn't the only one who