In another question where EU2 was behaving differently to EU5 I commented:
For what its worth, trust is listing EU2 as “Release: Summer ’15 Patch 9.6” and EU5 as “Release: Summer ’15 Patch 10“. NA1 is on 9.6. I can’t find anything that would explain the differences between 9.6 and 10.
Which left me wondering, How can we tell what is changing with each patch release?
The triannual Summer, Spring and Winter major releases are well documented.
Where is the documentation for the contents of each intermediate patch release?
@TimChadwick helpfully pointed me to https://success.salesforce.com/issues_releases_view?release=190000000, which shows the list of main pods and their current patch status.
What I found more interesting was the release=190000000 in the query string.
196010000Summer ’15 Patch 10.0
194012000Spring ’15 Patch 12.0
192013000Winter ’15 Patch 13.0
This certainly seems useful, but applying it to the Summer’15 Patch 9.6, which I know existed as I noted it in the question, didn’t reveal any known issues.
Also, not everything that is being patched appears as a known issue. Is there any other source of changes in the patches?
And you have inferred the correct structure of the query param. You can even see this if you use the following:
You will see the current release. But the following indicates release in progress (as of the time of this post).
Clearly the release team is trying to communicate the information you want, it just isn’t very clear how to get to that information in some instances, and how it works (what is the numeric code that corresponds to a release, what are the patch numbers, when were they released, why is history incomplete, etc.)
I would suggest that this should be an idea on IdeaExchange, to the effect of, “Greater transparency and clarity in patch releases with regards to affected features, services, instances, and history.”
I know that “have you tried IdeaExchange?” can start to be a pat answer from a Salesforce employee (like me), but I truly believe that this is precisely the kind of feedback that the technology teams should be getting from customers and implementers. You can also use it to suggest the level of documentation needed.
In fact, there is already an idea that is asking just that, 2 years old, with a measely 3 votes. If everyone who up voted for this question had voted instead, it would have increased the point count by times.
Some specific comments to clarify how what has been done already could be improved might also be good.
(Strike that…4 votes, as I just voted.)
Please vote for Easy navigation/searching for Scheduled/Fixed issues by release.
Update: Current idea point count as of Dec 2017 is at 390. If you up-voted the question above (or for this answer), then please vote for the idea!