Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
N
neoppod
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Jérome Perrin
neoppod
Commits
1705d828
Commit
1705d828
authored
Mar 09, 2016
by
Julien Muchembled
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Release version 1.6.2
parent
24780e8e
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
12 additions
and
1 deletion
+12
-1
CHANGELOG.rst
CHANGELOG.rst
+11
-0
setup.py
setup.py
+1
-1
No files found.
CHANGELOG.rst
View file @
1705d828
Change History
==============
1.6.2 (2016-03-09)
------------------
- storage: switch to a maintained fork of MySQL-python (mysqlclient)
- storage: for better performance, the backend commit after an unlocked
transaction is deferred by 1 second, with the hope it's merged by a
subsequent commit (in case of a crash, the transaction is unlocked again),
so there are only 2 commits per transaction during high activity
- client: optimize cache by not keeping items with counter=0 in history queue
- client: fix possible assertion failure on load in case of a late invalidation
1.6.1 (2016-01-25)
------------------
...
...
setup.py
View file @
1705d828
...
...
@@ -54,7 +54,7 @@ else:
setup
(
name
=
'neoppod'
,
version
=
'1.6.
1
'
,
version
=
'1.6.
2
'
,
description
=
__doc__
.
strip
(),
author
=
'NEOPPOD'
,
author_email
=
'neo-dev@erp5.org'
,
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment