* 3.3 release notes scaffolding
* Add modified version of internal release notes (to be further improved)
* slightly updated release notes
* Add another char to CSE ID regex
* Add 3.3 to version switcher
* removed empty sections
* Amend text about DC2DC in release notes.
* Move DC2DC description to Release Notes
* Add links to highlights and release notes
* Add placeholder for 3.3 upgrading
* renamed from server-global to server-level
* changed wording
* port changes from branch 3.3.0
* Update VERSIONS with 3.3 CSE IDs and sitemap settings
* integer overflow in Constituent could seize operation of Agency
* less likely integer overflow on double conversion
* less likely integer overflow on double conversion
* changed comparison to integer comparison as suggested by @neunhoef
* fix some deadlocks found by evil lock manager (tm)
* fix duplicate lock
* fix indentation
* ensure proper lock dependencies
* fix lock acquisition
* removed useless comment
* do not lock twice
* create either a V8 transaction context or a standalone transaction context, depending on if we are called from within V8 or not
* AQL micro optimizations
* use explicit constructor
* only use V8DealerFeature's ConditionLocker for acquiring a free V8 context
entering and exiting the selected context is then done later on without having to hold the ConditionLocker
* remove some recursive locks
* Disable custom deadlock detection when Thread Sanitizer is enabled
* Changing ifdef's
* grr
* broke gcc
* Using atomic for ApplicationServer::_server
* fix premature unlock
* add some asserts
* honor collection locking in cluster
* yet one more lock fix
* removed assertion
* some more bugfixes
* Fixing assert
(cherry picked from commit 1155df173bfb67303077fbe04ee8d909517bfd21)
* Fixing an issue with intermediate commits
(cherry picked from commit 7f61fb9be0f22904be21e9dd26c3870035a5b318)
* Only check collection counts without intermediate commits
* Fixing assert
For example, the following log level now does not cause a warning anymore
v8 = trace
previously the log levels had to be specified without any whitespace around
* Add WITH to graph traversal syntax
* State clearer what where whitespace is ignored in conf files
* Add cross-references between POSITION() and CONTAINS()
* Mention GeoJSON in the description of the useLonLat option
* Troubleshooting: unexpected long running queries
Add remark that collection literals are inferior to FOR constructs and should not be used accidentally instead of variable names
* Add storage engine comparison table, replace hint to note that users might want to pick RocksDB for an installation
* CSS: No margin extra margin after last paragraph in callouts / hint boxes
Jan Christoph Uhde
Simran
Simran Brucherseifer
jsteemann
Heiko
Jan
Simon Grätzer
Max Neunhoeffer
Wilfried Goesgens