[MB-11716] Release notes for 2.5.0 are missing MB-9147 Created: 13/Jul/14  Updated: 13/Jul/14

Status: Open
Project: Couchbase Server
Component/s: documentation
Affects Version/s: 2.5.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Major
Reporter: Patrick Varley Assignee: Ruth Harris
Resolution: Unresolved Votes: 0
Labels: releasenote
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Flagged:
Release Note
Is this a Regression?: Unknown

 Description   
The release notes for 2.5.0 should mention that MB-9147 is fixed. High number of customers have hit this problem.




[MB-11708] memcached_version is wrong Created: 11/Jul/14  Updated: 11/Jul/14

Status: Open
Project: Couchbase Server
Component/s: build
Affects Version/s: 3.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Minor
Reporter: Patrick Varley Assignee: Trond Norbye
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Triage: Untriaged
Operating System: Centos 64-bit
Link to Log File, atop/blg, CBCollectInfo, Core dump: [vagrant@localhost ~]$ uname -a
Linux localhost.localdomain 2.6.32-431.el6.x86_64 #1 SMP Fri Nov 22 03:15:09 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
[vagrant@localhost ~]$ /opt/couchbase/bin/cbstats 192.168.71.103:11210 all -b XDCR | grep memcached
 memcached_version: 2.0.1-macosx-233-g8e4053f
[vagrant@localhost ~]$
Is this a Regression?: Unknown

 Description   
On the Centos 6u5 x86_64 memcached_version is wrong:

[vagrant@localhost ~]$ uname -a
Linux localhost.localdomain 2.6.32-431.el6.x86_64 #1 SMP Fri Nov 22 03:15:09 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
[vagrant@localhost ~]$ /opt/couchbase/bin/cbstats 192.168.71.103:11210 all -b XDCR | grep memcached
 memcached_version: 2.0.1-macosx-233-g8e4053f
[vagrant@localhost ~]$


 Comments   
Comment by Dave Rigby [ 11/Jul/14 ]
I had a quick look at this - it's created by the output of `git describe` - which shows the last tag on the memcached tree. It just so happens this is "2.0.1-macosx". We should probably tag the 3.0 branch before it goes out which will "fix" this.

Either way the hex string (8e4053f) *is* the SHA of the most recent commit on the 3.0 memcached branch, so it is useful to a degree.
Comment by Phil Labee [ 11/Jul/14 ]
This is a code error and not the resposibility of the build team. No part of the product should compute any sort of version string based on git tags, mostly because they are unreliable. This has been our policy for almost a year.

From:

    http://hub.internal.couchbase.com/confluence/display/CR/Branching+and+Tagging

Although "git describe" accurately describes the state of a repo, it may not accurately describe the product being release. If exposed to the end-user, this may cause confusion, so it is important that the output of "git describe" is NOT used to describe the product. This is in Help :: About dialog boxes in UIs, text files like README and VERSION.txt, and in log files and diagnostic tools that report the version of the installed product.
Comment by Phil Labee [ 11/Jul/14 ]
assuming this is a bug in memcached

If it's a bug in some other project (e.g. couchbase-cli) please reassign.




Generated at Sun Jul 13 20:12:06 CDT 2014 using JIRA 5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9.