Opened 12 years ago
Closed 12 years ago
#558 closed defect (fixed)
CAPI library version in 3.3.4 inferior to the one in 3.3.3
Reported by: | strk | Owned by: | pramsey |
---|---|---|---|
Priority: | blocker | Milestone: | 3.3.5 |
Component: | Build/Install | Version: | 3.3.4 |
Severity: | Unassigned | Keywords: | |
Cc: |
Description
Release 3.3.3 was shipped with CAPI library version 1.7.4 while 3.3.4 went out with version 1.7.3 -- this prevents the newer version from replacing the older version.
Change History (5)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
According to the git-svn view of this, the "3.3.3" tag is at r3586, but the commit announcing the tag was r3580. Between the two there have been another 2 commits, one of which was "Update version number after tag" which advanced the CAPI one to 1.7.4.
So I suspect the release went out NOT from the tag but from the branch, thus getting 1.7.4 in it.
On another branch (was it "trunk" at that time?) r3581 only updated the C++ version to 3.3.4 and left the CAPI one to where it was at tag time (thus 1.7.3).
Paul: you'd better find a lawyer ! :P
comment:3 by , 12 years ago
comment:4 by , 12 years ago
sounds like "work done in tag" rather than in branch, basically making the tag not immutable. r3582 and r3586 shouldn't have been there.
Compare with 3.3.2: http://trac.osgeo.org/geos/log/tags/3.3.2
And with 3.3.4: http://trac.osgeo.org/geos/log/tags/3.3.4
NOTE: 3.3.2 shipped with 1.7.2 so the real bug (gap introduced) was in 3.3.3
Weird, as r3560 ("Prepare for 3.3.3") was setting it to 1.7.3 -- I'm puzzled