Re: Does a change approved for f39 need reapproval for f40?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On Mon, Oct 30, 2023 at 2:06 PM Jonathan Wakely <jwakely@xxxxxxxxxx> wrote:
Well it looks like I took too long to do the deferral to F40, and so
FESCO dropped the change:
https://pagure.io/fesco/issue/3059#comment-875144

So now do I need to re-submit as a fresh change for F40?

My reading of the email replies to the FESCO minutes when they announced this (https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/thread/E3M624WQFJV4L5NCJBA3UC746Z7BWNO5/#TMIPXR25CJR72BUMXHKTVICUKVUU5REM) is that they want an entirely new change proposal for it... since they apparently didn't think anyone was working on it and that it was completely abandoned even though you had emailed that you were working on it.

-Ian
 

On Fri, 11 Aug 2023 at 20:49, Fabio Valentini <decathorpe@xxxxxxxxx> wrote:
>
> On Fri, Aug 11, 2023 at 9:43 PM Ben Cotton <bcotton@xxxxxxxxxxxxxxxxx> wrote:
> >
> > On Fri, Aug 11, 2023 at 2:56 PM Jonathan Wakely <jwakely@xxxxxxxxxx> wrote:
> > >
> > > This change got approved  for f39 but couldn't be done in time:
> > > https://fedoraproject.org/wiki/Changes/F39ModernizeTBB
> > >
> > > Does it need to be re-proposed and approved for f40, or can we just do it now? (in a side tag, as planned, of course).
> >
> > No, just do it:
> >
> > > Changes that cannot be completed will automatically be deferred to the next release and do not require re-submission unless substantial revisions are made.
>
> Speaking with my packager and FESCo hats on, I think it would also
> still be OK to push the change to both F40 *and* F39, so there
> wouldn't even be a need to defer at all. If you want to go this route,
> it might be good to ask FESCo for guidance (i.e. file a ticket), but I
> think the likelihood that we'll just tell you "go ahead with the
> changes in both F40 and F39" is pretty high. :)
>
> Fabio
> _______________________________________________
> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux