Tag releases as stable, rc, beta, alpha, milestone, snapshot
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Drizzle |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
We should tag our releases with one of the following so it is obvious what type of release it is:
- stable
- rc
- beta
- alpha
- milestone
- snapshot
Of the above, "snapshot" should be default and has the meaning of not being a release. In the current build system this would be everything that has a 4 digit version number. Example: 2012.01.07.2489 would become 2012.01.
The other tags would be used with their common meanings together with a proper release (ie you did a bzr tag, make dist and uploaded a release somewhere). Meaning of "milestone" is "none of the above" ie less than alpha quality.
Currently the version is deduced from bzr tags and bzr revno information automagically in m4/pandora_
Related branches
- Vijay Samuel: Needs Fixing
- Mark Atwood: Needs Fixing
- Drizzle Merge Team: Pending requested
-
Diff: 304 lines (+50/-40)15 files modified.bzrignore (+2/-0)
Makefile.am (+1/-15)
client/drizzle.cc (+2/-2)
client/drizzledump.cc (+2/-2)
configure.ac (+2/-2)
docs/installing/redhat.rst (+3/-1)
drizzled/main.cc (+2/-2)
drizzled/sys_var.cc (+4/-4)
m4/pandora_vc_build.m4 (+23/-3)
plugin/auth_ldap/docs/index.rst (+3/-3)
plugin/innobase/xtrabackup/xtrabackup.cc (+1/-1)
support-files/drizzle.pc.in (+1/-1)
support-files/include.am (+1/-1)
tests/valgrind.supp (+2/-2)
win32/config.h (+1/-1)
| Changed in drizzle: | |
| status: | New → Fix Released |
