Tasks to do before 5.1 production release
Things to do before we consider 5.1 a production release:
1) Add Debian and CentOS platforms. (Ignore opensuse and fedora?)
2) signed packages
Blueprint information
- Status:
- Not started
- Approver:
- Henrik Ingo
- Priority:
- Essential
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- None
- Definition:
- New
- Series goal:
- Accepted for mepsql51
- Implementation:
-
Unknown
- Milestone target:
-
5.1
- Started by
- Completed by
Whiteboard
(Potentially low hanging fruit is marked as optional.)
# Test and release DEB for Ubuntu, Debian
DONE ## Optional: See if it is easy to generate the debian/ directory so that package names come from $MYSQLFORK variable (like done with bintar).
DONE ## Optional: Put more of this stuff into .mysql_version file and add comments. This one file should eventually contain all of the configurable parts on the bakery scripts level. (Of course, mysql source code itself has things like version number, etc...)
DONE # Deb files versioning needs to include distro codename. (Percona does this correctly.)
DONE # Review and start using other "fork branding" options, --with-
DONE # Files (including top directory) in bintar have so little permissions that mysqld won't start when untarred. BuildBot umask issue?
# RPM packages for CentOS/RHEL. (later fedora, possibly opensuse)
# signed packages (also bintar, source or at least md5sums)
# Decide and fix Flascache issue +bug/717423
