From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30412 invoked by alias); 15 May 2018 13:27:06 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 30403 invoked by uid 89); 15 May 2018 13:27:05 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=genuinely, compelled, faith, comfortable X-HELO: mail-ot0-f177.google.com Received: from mail-ot0-f177.google.com (HELO mail-ot0-f177.google.com) (74.125.82.177) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 15 May 2018 13:27:03 +0000 Received: by mail-ot0-f177.google.com with SMTP id n1-v6so145526otf.7 for ; Tue, 15 May 2018 06:27:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=AKFeSQXDB4A3KLbNXrwrRi2ZPKDX3MUVoOU1eDR6AE8=; b=bbnA19sMmikVAOIyMk+Yxch9W1yFqF+27N1JkgjIowG5ixJXhEB97m9yG6hKe650vH vRqMYVVNcK6nFaLIDLi5jGKZephxdSPEpm8poTG5jlzQYlI6YQRCHBlADNxEzCjK35eA bauLDRAGajEjmar/4GnCNevw0oxy4OUHiW6Fd4G6oFFZ87a9vy7CLJvdS+Nz2VuFVVcX 3UjrH2nvxcUruqVXJFPUgD4SbJ6i2jurDSE9I/iPMW+zqb/2HE8TEQ4lFvyY41j+/fVh AgU6lSMCXmNdyLqisSam7R0jBvKKmw6pY5p8iQsnjPyd1YvUUtaQtnMegJQkQWblFXzq wBvA== X-Gm-Message-State: ALKqPwfsoGG/+DpDcKaYjsSqXLY57MglHT/zr901U6ny/Tc1d38hmyEq uz6NWjs7zFZSp2v369GIAmlYp6VheYegFZEChfKrw+zDTCI= X-Google-Smtp-Source: AB8JxZo2s3bR4stokqPfIbwSrVWUQtpoiRGF4rso5QdlG8NY52ws2fbtVRrinoBGOobcH2R7H0KbivtGYVBO9Mq9wcs= X-Received: by 2002:a9d:1e1:: with SMTP id e88-v6mr10914815ote.10.1526390821480; Tue, 15 May 2018 06:27:01 -0700 (PDT) MIME-Version: 1.0 References: <5afa206a.1c69fb81.2121e.da3a@mx.google.com> In-Reply-To: <5afa206a.1c69fb81.2121e.da3a@mx.google.com> From: Adam Dinwoodie Date: Tue, 15 May 2018 14:37:00 -0000 Message-ID: Subject: Re: Request new Ruby release To: cygwin@cygwin.com Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2018-05/txt/msg00194.txt.bz2 On Tue, 15 May 2018 at 00:49, Steven Penny wrote: > fact. example is the Git package, which as of this writing is totally up to > date: > - http://cygwin.mirrors.hoobly.com/x86_64/release/git > - http://github.com/git/git/releases I've been avoiding this thread as I haven't had anything productive to add. However a package I maintain has now been invoked as an example, and I feel compelled to respond; I am not comfortable with my work being held up to shame other volunteer maintainers. I entirely understand the desire for up-to-date packages to be available, and clearly there are vast swathes of our packages that aren't kept at the bleeding edge of the upstream release tracks. However I don't think this email trail is a good way to encourage maintainers to put in the effort required to keep things up to date. Maintainers, at least for the most part, are going to be well aware when their packages aren't the latest code, and equally be aware of the possibilities of releasing test packages. Pointing these things out, particularly repeatedly, is unlikely to be well received. For anyone who wants to see Cygwin packages updated, a single prompt to the maintainer is occasionally useful, but further prompts are likely to be taken as hassling, not as helpful. Beyond that, I expect most maintainers will have an idea of what other people could do to help if someone offered; I know for myself I can point at specific things other people could offer to help for each of my packages, and I imagine other maintainers would also be able to answer a question of "I'd like to see this updated, what can I do to help?", even if the answer is sometimes going to be "nothing". As others have pointed out, the Cygwin package maintainers are volunteers, using their own time and resources. I don't think any of them will appreciate being described as acting in bad faith, myself included (and while Git is up-to-date, other packages I maintain aren't, for a variety of reasons, so I very much take the description as being levelled at me as much as anyone else). If someone genuinely thinks a package maintainer is acting in bad faith, or otherwise not keeping up with their responsibilities as a maintainer, *and* they're able and willing to put in the effort to take over the maintainership, that's a discussion we can have. However, certainly in the cases of Ruby and GCC and their related packages, as Yaakov has said, I don't think there's any question from the other maintainers or the folk who run the Cygwin project as a whole, that they are working in good faith and keeping up with their responsibilities to the project, even if individuals would prefer different behaviour. This thread is not going to get GCC, Ruby, or any other package updated more quickly than it otherwise would. I'd recommend folk who want to see what they can do to get things updated ask what they can do to help, and accept that the answer may be "nothing". Adam -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple