Re: Ruby EOL in Cygwin 3.4.9?

[gs-cygwin.com@gluelogic.com]

On Wed, Oct 11, 2023 at 09:55:04PM -0500, Eric D Hendrickson via Cygwin wrote:
> Sorry for the unclarity - I meant this for the whole list - not just you.
> 
> Thank you so much for taking the time to respond.  Like you said, this
> really is all volunteers.
> 
> For the whole list:
> 
> Totally taking into account the all volunteer nature of Cygwin, would it
> make sense to defer on further non-emergency releases of Cygwin until all
> packages that are EOL have been updated?  Since this is the case with ruby,
> I am guessing it's likely the case with other packages in Cygwin too.
> 
> Is there a Issues log of some sort (ala github) for Cygwin somewhere, so
> that I can document this in the backlog and come back later to investigate
> this myself if I have time this winter?
> 
> 
> On Wed, Oct 11, 2023 at 8:11 PM Eliot Moss <moss@cs.umass.edu> wrote:
> 
> > On 10/11/2023 6:36 PM, Hendrickson, Eric D wrote:
> > > Hi Eliot,
> > >
> > > Thanks for responding.  That makes total sense.
> > >
> > > Totally taking into account the all volunteer nature of Cygwin, would it
> > make sense to defer on further non-emergency releases of Cygwin until all
> > packages that are EOL have been updated?  Since this is the case with ruby,
> > I am guessing it's likely the case with other packages in Cygwin too.
> > >
> > > Is there a backlog for Cygwin somewhere, so that I can investigate this
> > myself if I have time this winter?
> > >
> > > Thank you and all the best,
> > > Eric
> > >
> > > -----Original Message-----
> > > From: Eliot Moss <moss@cs.umass.edu>
> > > Sent: Wednesday, October 11, 2023 5:03 PM
> > > To: Hendrickson, Eric D <edh@optum.com>; cygwin@cygwin.com
> > > Cc: Eric @ Gmail <ericdavidhendrickson@gmail.com>
> > > Subject: Re: Ruby EOL in Cygwin 3.4.9?
> > >
> > > On 10/11/2023 12:37 PM, Hendrickson, Eric D via Cygwin wrote:
> > >> Hello all,
> > >>
> > >> As a ~25 year user and sometime contributor to Cygwin, I support Cygwin
> > here at my place of work.  Does anyone know why we are deploying Ruby 2.6
> > which EOL about 18 months ago?
> > >>
> > >> https://www.ruby-lang.org/en/downloads/branches/
> > >>
> > >> I'm concerned about proliferation of EOL versions of Ruby in case some
> > security risk / 0Day is identified.
> > >>
> > >> Please advise.
> > >> Eric Hendrickson
> >
> > You should send such things to the list, not me.  I'm just
> > a user who has only made occasional small contributions ...
> >
> > Eliot
> >
> > > If nobody has responded I can give a generic response:
> > > "Because cygwin is all volunteer and someone has not volunteered, or did
> > volunteer and is behind, or fell off the radar."
> > >
> > > Someone else will know how to look up if there is a currently registered
> > volunteer for Ruby ...
> > >
> > > Eliot Moss
> > >
> > >> This e-mail, including attachments, may include confidential and/or
> > >> proprietary information, and may be used only by the person or entity
> > >> to which it is addressed. If the reader of this e-mail is not the
> > >> intended recipient or intended recipient’s authorized agent, the
> > >> reader is hereby notified that any dissemination, distribution or
> > >> copying of this e-mail is prohibited. If you have received this e-mail
> > >> in error, please notify the sender by replying to this message and
> > delete this e-mail immediately.
> > >>
> > >
> > > This e-mail, including attachments, may include confidential and/or
> > > proprietary information, and may be used only by the person or entity
> > > to which it is addressed. If the reader of this e-mail is not the
> > intended
> > > recipient or intended recipient’s authorized agent, the reader is hereby
> > > notified that any dissemination, distribution or copying of this e-mail
> > is
> > > prohibited. If you have received this e-mail in error, please notify the
> > > sender by replying to this message and delete this e-mail immediately.
> >
> >


On Wed, Oct 11, 2023 at 09:55:04PM -0500, Eric D Hendrickson via Cygwin wrote:
> For the whole list:
> 
> Totally taking into account the all volunteer nature of Cygwin, would it
> make sense to defer on further non-emergency releases of Cygwin until all
> packages that are EOL have been updated?

Absolutely not.  That makes *zero* sense for an all volunteer group.

Not every single package is important to everyone.
(I am speaking personally, as maintainer of a single package on Cygwin.)

You care about Ruby?  Good.
I do not use Ruby, so that is not important *to me*.

If some specific packages are important to you, please consider finding
the maintainers of those packages and offering to help maintain those
packages.

https://cygwin.com/cygwin-pkg-maint

There are many ruby-* packages that have been orphaned.  Have at it. :)

Cheers, Glenn