Re: Fedora Lifecycles: imagine longer-term possibilities

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

 



Dne 16. 11. 18 v 10:38 Vít Ondruch napsal(a):
> Dne 16. 11. 18 v 0:54 Jason Tibbitts napsal(a):
>>>>>>> "MM" == Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> writes:
>> MM> How would we balance this with getting people new stuff fast as
>> MM> well?
>>
>> Wait, what?  Certainly you're not suggesting trying to do an extended
>> lifecycle that also gets all the new stuff.  That's seems like a
>> contradiction in terms.
>
> This last paragraph you could already apply to EPEL and this is
> specifically reason why I don't bother to maintain anything in EPEL.
>

Just to clarify, I don't mind backporting security patches into Ruby
1.8.7 in RHEL6, but if there were since that time Ruby 1.9.3, 2.0.0,
2.1, 2.2, 2.3, 2.4 and 2.5 in modules, SCLs or whatever else, I can tell
you that would become quickly PITA. I am not even mentioning the whole
Ruby ecosystem ....


Vít
_______________________________________________
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