[Exist-development] Wrong git tag and version in eXist-db 3.0

[Adam R. <ad...@ex...>]

Dear developers,

There seems to have been a problem with creating and releasing eXist-db 3.0.

The Git tag "eXist-3.0" points to commit acd0c14, but should have been
9911af8. This leads to concrete problems, with builds of eXist-3.0 tag
reporting the wrong version, to see what I mean:

$ git clone https://github.com/exist-db/exist.git
$ git checkout eXist-3.0
$ cat build.properties

project.name = eXist-db
project.version = 3.0.RC2
project.version.numeric = 3.0.3
project.source = develop
project.codename = Berlin

...

So this leads to eXist-3.0 reporting its version as "3.0.RC".

The main problem here is that when users report issues via the mailing
list or GitHub and they ask us which version they are running, they
will tell us 3.0.RC2 which is incorrect. It is very likely we will
then tell them to install the final version of eXist-3.0 which will
waste their time and ours and not solve anything... especially in a
few years when we forget and are confused why after upgrading they are
still running the same version.

I am also going to assume that as releases must always be built from
git tags, that the actual binary release of eXist-3.0 exhibits exactly
the same problem as the source base.

So I think we can assume that 3.0 has a critical problem, in so far as
it identifies itself as the wrong version, which is going to confuse
everyone.

I think out best option is to immediately create a 3.0.1 release and
announce that. We should definitely NOT try and fix 3.0 and re-release
it, having two versions of "3.0" which are different will only add to
the chaos.

If you agree, this is the process that I would suggest to get to 3.0.1
so that we don't have any more version issues:

1) Update build.properties in the develop branch to reflect 3.0.1.RC1
and commit (should have been does as first commit after 3.0
release!!!)

2) Make any **critical** fix commits to develop branch (maybe none,
although I know Joe Wiz would deeply like to see newer eXide version)

3) (Assuming you still don't want to do Release Candidates for some
reason) Update build.properties in develop branch to be 3.0.1 and
commit

4) tag (and preferably sign) eXist-3.0.1 as the HEAD of develop branch and push

5) Update build.properties in develop branch to be 3.0.2.RC1 and commit and push

6) Checkout the eXist-3.0.1 tag, build the code and release the binary files



p.s. I get that mistakes happen and that is fine, but let's just get
this done and sorted ASAP so that we can reduce the window of
confusion and frustration for both our users and developers.

Cheers Adam.


-- 
Adam Retter

eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb