Richard Levitte

All that being said, I agree that our coding style guide needs an update.

There are quite different views on this. For example, one might consider browser caches, and https://jquery.com/download/#using-jquery-with-a-cdn : > ... This also offers an advantage that if the visitor to your...

I know who you work for. However, if a browser sees a reference to code.jquery.com and another to www.openssl.org, it will load it twice, even if pinned on the same...

So, I guess it should be something like "for current development as well as all supported releases". That would fit what we put on display, no? (3.2 in alpha state...

I'd like to argue that they are supported, just not for free. But hey, if you want to be wordy, how about "for current development as well as all supported...

It means that there's a disconnect between CHANGES in the master branch and CHANGES in 1.1.1. We've been staggeringly sloppy with those files in the last few years.

What's happening in practice is that while the CHANGES in 1.1.1 is better for 1.1.1, we're using CHANGES from master on our web site, for all releases. We need to...

This is, BTW, a web problem, so I'm moving this over to that repo (on of github's newer features)

Upon closer inspection of the web page, it *does* have an explanation: > When a release is created, that branch is forked off, and its changelog is also forked. For...

I think I'm leaning on the cautious side re the default. @karel-m said it a lot better