Re: Should we have a release manager for each release? (or, "who owns rawhide"?)

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

 



On Fri, 2018-02-16 at 07:21 -0500, Matthew Miller wrote:
> On Thu, Feb 15, 2018 at 03:22:29PM -0800, Adam Williamson wrote:
> > I mean...#fedora-releng ? This is kinda what release engineering *does*
> > - they engineer releases. So if a release is not being engineered
> > optimally, go ask release engineering. I guess I'm just not seeing what
> > all would actually be improved by putting another fancy named position
> > into the loop.
> 
> Well, I was looking at
> https://docs.pagure.org/releng/index.html#things-we-do, and it says
> 
> "Report progress towards release from branched creation on."
> 
> ... which implies that it's someone else's thing up until the branch. 

Well, 'report' is different from 'monitor'. In practice, releng folks
certainly do keep an eye on and work to fix Rawhide composes. We could
certainly clarify this stuff in some way, though, I guess.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [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