mahara-contributors team mailing list archive

[Aaron Wells <1463630@xxxxxxxxxxxxxxxxxx>]

Okay, I've uploaded new 1.10.4 release packages that have the correct
release string. So now if you download the releases from Launchpad, they
will read "1.10.4" instead of "1.10.5testing".

I've also bumped the database version number, so if you replace your
erroneous "1.10.5testing" packaged install with this new package, it
will change it to read "1.10.4".

(On the git side of things, there actually hadn't been any further
commits in the 1.10_STABLE git branch since the 1.10.4 release, so I
took care of this in the git history by adding a new commit to the top
of the 1.10_STABLE branch which bumps the DB version and changes the
release string from 1.10.5testing to 1.10.4. I then moved the
1.10.4_RELEASE signed tag to point at this new commit. Lastly I created
another commit that changes the release back to 1.10.5testing and bumps
the DB version again. I considered doing a git push --force to get rid
of the erroneous commit from our history, but I decided against it
because it might make future merges just a tiny bit more complicated. Of
course, git doesn't really support moving tags around, so anyone who has
already fetched the old 1.10.4_RELEASE tag will not see the new one. But
that's not such a big deal.)

Cheers,
Aaron

** Summary changed:

- wrong release number for 1.10.4?
+ Wrong release number in 1.10.4 tarball

** Changed in: mahara
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1463630

Title:
  Wrong release number in 1.10.4 tarball

Status in Mahara ePortfolio:
  Fix Released

Bug description:
  In the archive mahara-1.10.4.zip and mahara-1.10.4.tar.gz, each
  'lib/version.php' has release number '1.10.5testing'.

   $config->release = '1.10.5testing';

  This may be wrong number, and I wonder if some 1.10.5testing codes
  contaminate in 1.10.4 archives.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1463630/+subscriptions