gerrit/ReleaseNotes/ReleaseNotes-2.8.6.txt
Yuxuan 'fishy' Wang 4f5ad9d313 Use buck rule for ReleaseNotes instead of Makefile
This eliminates the last Makefile in our code base.

Also change the section style within ReleaseNotes from asciidoc style to
asciidoctor style.

Also I feel that put images/link.png under ReleaseNotes and deal with
all the resource packing is too stupid, so I used the unicode emoji
instead of the picture ("🔗"). If this is too crazy, we can also use "#"
instead :) This also affects documentation rendering.

Other side effects:

1. The css of release notes switched from default asciidoc css into
default asciidoctor css.
2. The section anchors for ReleaseNotes/index.html changed from "2_13"
to "s2_13", because asciidoctorj is unhappy with anchors without
letters.

Change-Id: I4adf2ce090385cc6b699445012f10a009892aaac
2016-05-17 23:23:31 +00:00

45 lines
1.6 KiB
Plaintext

= Release notes for Gerrit 2.8.6
There are no schema changes from link:ReleaseNotes-2.8.5.html[2.8.5].
Download:
link:https://www.gerritcodereview.com/download/gerrit-2.8.6.war[
https://www.gerritcodereview.com/download/gerrit-2.8.6.war]
*Warning*: Support for MySQL's MyISAM storage engine is discontinued.
Only transactional storage engines are supported.
== Bug Fixes
* link:https://code.google.com/p/gerrit/issues/detail?id=2034[Issue 2034],
link:https://code.google.com/p/gerrit/issues/detail?id=2383[Issue 2383],
link:https://code.google.com/p/gerrit/issues/detail?id=2702[Issue 2702]:
Fix race condition in change merge queue when using Cherry-Pick submit
strategy.
+
There was a race in the merge queue between changes submitted via
the UI, and merges scheduled by the background merge queue reload.
+
This resulted in multiple submit actions being scheduled, leading
to corrupt changes.
+
Execute cherry-pick submit DML operations in a database transaction
boundaries. In combination with implemented transaction management
for Jdbc dialects it solves the problem recovering from collisions
between interactive actions and background jobs.
* In gwtorm the LIMIT clause was only honored when followed by a
constant integer.
+
When followed by a placeholder "?" it wasn't included in the generated database
query. This caused poor performance when moving to the next change page for very
big projects.
* Fix sporadic SSHD handshake failures
(link:https://issues.apache.org/jira/browse/SSHD-330[SSHD-330]).
== Updates
* gwtorm is updated to 1.7.1
* sshd is updated to 0.11.1-atlassian-1