MySQL Bugs: #71072: Please, make sure Launchpad sources are updated before announcing release

Bug #71072	Please, make sure Launchpad sources are updated before announcing release
Submitted:	4 Dec 2013 8:44	Modified:	2 Apr 2014 11:58
Reporter:	Valeriy Kravchuk	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Packaging	Severity:	S3 (Non-critical)
Version:	5.1.73, 5.5.35, 5.6.15, 5.7.3	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	launchpad, processes, Release

Description:
It's already announced in public that MySQL 5.1.73 and 5.5.35 are officially released on December 3. At the same time, I do not see updated sources at Launchpad:

[openxs@chief mysql-5.5]$ cd ../mysql-5.1
[openxs@chief mysql-5.1]$ bzr pull
Using saved parent location: http://bazaar.launchpad.net/~mysql/mysql-server/5.1/
No revisions to pull.
[openxs@chief mysql-5.1]$ bzr version-info
revision-id: balasubramanian.kandasamy@oracle.com-20130909180712-0ewu3uqnwgb2urpg
date: 2013-09-09 20:07:12 +0200
build-date: 2013-12-04 10:39:54 +0200
revno: 4044
branch-nick: mysql-5.1

I think this is somewhat wrong.

How to repeat:
Try to pull sources of any version listed now and check version information there. Yet another example:

[openxs@chief mysql-5.5]$ bzr pull
Using saved parent location: http://bazaar.launchpad.net/~mysql/mysql-server/5.5/
No revisions to pull.
[openxs@chief mysql-5.5]$ bzr version-info
revision-id: balasubramanian.kandasamy@oracle.com-20131105070343-be7e1rgywdaeapof
date: 2013-11-05 08:03:43 +0100
build-date: 2013-12-04 10:36:09 +0200
revno: 4535
branch-nick: mysql-5.5
[openxs@chief mysql-5.5]$ grep -rn VERSION * | grep '5\.5\.3'
CPackConfig.cmake:67:SET(CPACK_PACKAGE_VERSION "5.5.34")
CPackSourceConfig.cmake:69:SET(CPACK_PACKAGE_VERSION "5.5.34")
include/config.h:614:#define PACKAGE_VERSION "5.5.34"
include/config.h:615:#define VERSION "5.5.34"
include/my_config.h:614:#define PACKAGE_VERSION "5.5.34"
include/my_config.h:615:#define VERSION "5.5.34"
include/mysql_version.h:13:#define MYSQL_SERVER_VERSION         "5.5.34"
info_macros.cmake:25:SET(VERSION "5.5.34")
make_dist.cmake:33:SET(VERSION "5.5.34")
^C

Compare dates, grep for version, do whatever you like - it's not 5.5.35 yet.

Suggested fix:
Please, make sure Launchpad repositories are updated before official email about the release is sent to MySQL Community.

Hello Valeriy,

Thank you for the report.
I couldn't find any updates either.

Thanks,
Umesh

Just a quick comment to clear up: the code WAS uploaded and it IS there. If you go browse the actual code you will see it. And e.g. this page shows all the new releases:

https://launchpad.net/mysql-server

However, some of the web pages on the site did not get updated to reflect the new code. E.g. this page for 5.7 shows the latest changes to the release:

https://code.launchpad.net/~mysql/mysql-server/5.7

But the same page for 5.6 does not.

This seems to be a problem with the Launchpad site, it gives inconsistent views of the code. We saw something similar with the previous set of releases too.

Current code is there, but it only appeared after this bug was reported, and it wasn't just a launchpad website delay, it also wasn't in lp: bzr at that time yet.

I did bzr pulls at about the same time and 5.6.15, 5.7.3 were not there yet,
they only appeared on a pull the next day (Dec. 5th), so two days delay between 
release announcement and availability of download files and bzr availability ...

Those who pushed were not aware this bug had been filed. In any case, it's not possible to have the sources pushed to LP until *after* the releases are official and the release branches have been tagged and merged back to the main development branches. Only then can we be 100% sure what is the correct version to push.

Our records show all branches were pushed to LP on the 4th, but exact time is not available. Due to the way bzr works, it's not (I think) possible now to see from LP when they were pushed, but I remember doing 5.7.3 very shortly after sending the announcement email. Maybe you checked early in the day, or there may be some internal delays. As noted above, Launchpad has had problems with getting web pages correctly updated to reflect the pushes.

I am closing this now. We know that getting the source out quickly is very important, and we have made some improvements to our processes to reduce any delays as much as possible. We can't make source available *before* release, but we will try to minimize delays as much as possible.