From: v.ondruch@tiscali.cz
To: ruby-core@ruby-lang.org
Subject: [ruby-core:91082] [Ruby trunk Misc#15534] Is there reliable way to check for new Ruby releases?
Date: Mon, 14 Jan 2019 14:34:40 +0000 (UTC) [thread overview]
Message-ID: <redmine.issue-15534.20190114143437.6a9e1dd9159f07ee@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-15534.20190114143437@ruby-lang.org
Issue #15534 has been reported by vo.x (Vit Ondruch).
----------------------------------------
Misc #15534: Is there reliable way to check for new Ruby releases?
https://bugs.ruby-lang.org/issues/15534
* Author: vo.x (Vit Ondruch)
* Status: Open
* Priority: Normal
* Assignee:
----------------------------------------
In Fedora, we are using https://release-monitoring.org/ to check for packages updates. Unfortunately, the content of https://cache.ruby-lang.org/pub/ruby/ is a bit inconsistent which makes this service unuseful.
If I open the page, there are listed a lot of packages, but for some reason, the later 2.6 releases are missing. There is a "stable" folder, but it contains just Ruby 2.3, which is quite stable, but I would expect there something more recent. There is a "binaries" folder, which contains some ancient binaries. There is also index.txt, which looks to be promising, but I am not sure.
So I wonder:
1. What is the most reliable version information
2. If it would be possible to clean up the repository
3. and make sure the information is consistent
--
https://bugs.ruby-lang.org/
next parent reply other threads:[~2019-01-14 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-15534.20190114143437@ruby-lang.org>
2019-01-14 14:34 ` v.ondruch [this message]
2019-01-17 4:01 ` [ruby-core:91137] [Ruby trunk Misc#15534] Is there reliable way to check for new Ruby releases? hsbt
2019-01-17 10:10 ` [ruby-core:91139] " v.ondruch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.issue-15534.20190114143437.6a9e1dd9159f07ee@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).