llvm dev - Feb 2019 - LLVM Releases page needs updating? (Still suggests using SVN)

Hi,

I've noticed that http://releases.llvm.org/ still mentions that
"Current" version
of LLVM Projects should be retrieved through SVN. With the GitHub mirror now
being
considered a "source of truth" for readonly checkouts, would it be
worth updating
that page and referring people to https://github.com/llvm/llvm-project instead?

(Though my only concern being, currently there are no RO-only mirrors on GitHub
for major projects since I presume majority of consumers will likely want to
checkout LLVM, Clang/CFE and LLD, it may be worth mirroring them separately.
I'm
not sure how well Git handled subtree checkouts, personally I've not had the
best
experiences, while a RO mirror is a lot more straightforward)

Thank you.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3992 bytes
Desc: S/MIME Cryptographic Signature
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20190217/3489071f/attachment.bin>

Hi Kristina,

On Sun, Feb 17, 2019 at 3:13 AM Kristina Brooks via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> I've noticed that http://releases.llvm.org/ still mentions that
"Current" version
> of LLVM Projects should be retrieved through SVN. With the GitHub mirror
now being
> considered a "source of truth" for readonly checkouts, would it
be worth updating
> that page and referring people to https://github.com/llvm/llvm-project
instead?
The page links to http://llvm.org/docs/GettingStarted.html#checkout
which already talks about Git instead of SVN, so updating the link
texts makes sense.

I've updated https://releases.llvm.org/ in http://llvm.org/r354269 but
it can take a while to show up on the page due to caching.

Thanks,
Hans