From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: update version on https://cygwin.com/ from 3.3.4 to 3.3.5?
Date: Tue, 14 Jun 2022 11:36:39 -0600 [thread overview]
Message-ID: <3d85c954-3c64-ba3d-2689-549517de645f@SystematicSw.ab.ca> (raw)
In-Reply-To: <b23ee85e01d64c6cbb8fc6f33f93e390@UPRD-EXCH13-M4.ida.org>
On 2022-06-13 18:39, Stone, Timothy M wrote:
>
> Hello,
>
> I've recently installe3d the latest version of cygwin, 3.3.5, which is listed as the lastest on the mirrors and also in cygwin's announcements.
>
> Unfortunately, the main page still lists the lastest as 3.3.4:
> https://cygwin.com/
>
> This is causing me problems getting cygwin approved here, because my IT folks don't think 3.3.5 is "real" and they think the last real version is 3.3.4.
>
> Is it possible to update the webpage?
I normally update the wikidata and link to announcement message promptly:
https://en.wikipedia.org/wiki/Cygwin
In the infobox for Stable release is a link to the announcement mailing
list post:
https://cygwin.com/pipermail/cygwin-announce/2022-May/010565.html
which should be considered more definitive than info on a web page::
seems like a weak excuse.
I don't know if the web site htdocs release can be made dynamic or
auto-updated during release?
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
prev parent reply other threads:[~2022-06-14 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 0:39 Stone, Timothy M
2022-06-14 8:48 ` Corinna Vinschen
2022-06-14 17:36 ` Brian Inglis [this message]
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-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3d85c954-3c64-ba3d-2689-549517de645f@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/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).