And there’s an issue with the signature of the .deb files:
An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://maven.xwiki.org releases/
However, now the release page already lists two “(…) important bugs have been discovered since XWiki 10.11.1 has been released”. Does this mean that a 10.11.2 is already pending and you do not recommend to upgrade to 10.11.1 in order not to break anything which worked before?
Additionally, www.xwiki.org is really slow for me today, the Release Notes page takes about 7 seconds (even on subsequent invocations) just to display anything - is it just me, or is it a server-side issue?
XS 10.11.1 fixes several blockers issues from 10.11 so it’s better than 10.11. However there are still 2 blockers in 10.11 that weren’t fixed in 10.11.2. So if you’re upgrading from 10.11, then you should upgrade to 10.11.1. If you’re using some older versions you should probably wait for 10.11.2.
Now it all depends on the bugs, what they impact and whether you use the impacted features or not.
@atallahade This is something we could put in the RN maybe?
OK I’m using “stable” one. Are you using “release” one since a long time ? It’s pretty rare to use it so it may have the issue since quite a while without us noticing.
From a user’s point of view, it’s interesting to distinguish between important bugs which have not yet been fixed in one specific release, and important bugs / regressions actually caused by this specific release.
If there would be a way to distinguish those two, it would help a lot with the update decision. What do you think?
I’m still on Xwiki 10.8.3 btw, would an update to 10.11 already be recommended once 10.11.2 is out, or do I still better wait a bit until async rendering and macro inline editing have matured a bit more?
yes it’s easy to do: you can click on each issue in the RN. This brings you to the issue page on jira.xwiki.org where you can see the “affects version” field which tells you when the bug was introduced.