Re: [modularity] Managing module lifecycles — let's talk!

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

 



On Fri, Aug 31, 2018 at 05:57:57PM +0200, Adam Samalik wrote:
> > I don't think we should use "rawhide" to mean "rolling updates", because it
> > also has the implication of "project devel stream".
> Just to make sure we're on the same page: I was talking about specifying an
> EOL field, not a stream name. Is that what you mean, too?

Yeah. I don't think rawhide is a good EOL field. (It's actually _better_ as
a stream name.)


> > I know there was pushback against naming stream branches "stable", so is
> > there a good _other_ way to offer this? If I name the stream branch "5"
> > after the upstream major release, how do I get people in the first case
> > seamlessly on to "6" when it comes out, whenever that is?
> "latest" would be the best option here:
> https://docs.fedoraproject.org/en-US/modularity/making-modules/naming-guidelines/#_module_stream_name

So, I guess "latest" and "stable" are probably good standard choices. I kind
of want "latest" and "slow". :)



-- 
Matthew Miller
<mattdm@xxxxxxxxxxxxxxxxx>
Fedora Project Leader
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[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