[ 
https://issues.apache.org/jira/browse/GEODE-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16431010#comment-16431010
 ] 

ASF subversion and git services commented on GEODE-5027:
--------------------------------------------------------

Commit ebce14894565900ebaf3730259a57b576f90ba80 in geode's branch 
refs/heads/develop from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ebce148 ]

GEODE-5027 Bump version to 1.6.0 and add v1.5.0 for testing

* I bumped the version in Version.java to 1.6.0 and added a 1.6 command set
  to CommandInitializer.
* I added v1.5.0 to geode-old-versions for backward compatibility testing.

* I removed junk in Version.java that hasn't been used since the SQLFire/GFX
  days.
* I also removed AcceptorImpl.VERSION which seemed to serve no good purpose.

* I added a unit test to make sure that folks update the CommandInitializer
  table when adding a new Version.  Without this test folks would have to run
  distributedTests to notice any problems with their changes.

* I changed CommandInitializer to not create new maps unless necessary.

* I fixed a test's expectation that the default connection pool exists after 
starting
  a client cache.  Starting with 1.5 the pool isn't created until it's needed.

This closes #1753


> Bump version to 1.6.0
> ---------------------
>
>                 Key: GEODE-5027
>                 URL: https://issues.apache.org/jira/browse/GEODE-5027
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Bruce Schuchardt
>            Assignee: Bruce Schuchardt
>            Priority: Major
>             Fix For: 1.6.0
>
>
> Bump the version to 1.6.0 and add 1.5.0 as an "old version" for backward 
> compatibility tests.
> Also clean up the CommandInitializer tables.  We're creating a new table for 
> every version even when there are no messaging changes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to