Skip to content

Commit

Permalink
[maven-release-plugin] prepare release xmemcached-2.2.0
Browse files Browse the repository at this point in the history
  • Loading branch information
@killme2008
killme2008 committed Oct 27, 2016
1 parent 8e98a6a commit 4dca575
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion pom.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
<modelVersion>4.0.0</modelVersion>
<groupId>com.googlecode.xmemcached</groupId>
<artifactId>xmemcached</artifactId>
<version>2.1.1-SNAPSHOT</version>
<version>2.2.0</version>
<name>xmemcached</name>
<description>Extreme performance modern memcached client for java</description>
<url>https://github.com/killme2008/xmemcached</url>
Expand Down

6 comments on commit 4dca575

@marstonstudio
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

any plans to issue 2.2.0 as a final release?

@killme2008
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@marstonstudio
It has released already.

https://github.com/killme2008/xmemcached/releases/tag/xmemcached-2.2.0

@marstonstudio
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, my apologies, I actually was referring to a final release for 2.2.1-beta with the elasticache fixes.

@killme2008
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@marstonstudio Have you test 2.2.1-beta on your production yet? I don't receive any feedback for it right now.

It still needs a few unit tests, i will try to release it as soon as i can.

@marstonstudio
Copy link

@marstonstudio marstonstudio commented on 4dca575 Feb 7, 2017 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have upgraded my DEV environment to use 2.2.1-beta now and will be deploying to PROD in one week. I can report back if it works or if any problems emerge.

No plans to explicitly test the elasticache failover in my environment. Will be on the lookout if we have an unplanned amazon failover and if it works.

@killme2008
Copy link
Owner Author

@killme2008 killme2008 commented on 4dca575 Feb 8, 2017 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@marstonstudio Tanks a lot.

I've test failover in our AWS development environment, it should be fine. If you have any problems ,please let me know.

Please sign in to comment.