We are releasing 7.1 beta releases with the package name drizzle7
Bug #913267 reported by
Henrik Ingo
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Drizzle |
Fix Released
|
Undecided
|
Unassigned | ||
| 7.1 |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
The version information provided in our recent beta releases is confusing. As discussed on drizzle-discuss@ [1] our next release (fremont series) is planned to be version 7.1. Hence the packages should be called drizzle7.
In addition to changing the package name in AC_INIT, please do a "grep -R drizzle7 *" to be aware of all the places where "drizzle7" is hard coded.
[1]: https:/
Related branches
lp:~hingo/drizzle/drizzle-the-version-is-7.1-not-a-date-and-certainly-not-7
- 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)
Revision history for this message
| Henrik Ingo (hingo) wrote | #1 |
Revision history for this message
| Henrik Ingo (hingo) wrote | #2 |
| summary: |
- If our next release is 7.1, then package name must be drizzle7.1 + We are releasing 7.1 beta releases with the package name drizzle7 |
To post a comment you must log in.
BJ explains that in Fedora the process becomes complicated if we change the package name for each release. We should instead consider doing drizzle-<version> like everyone else does. See the drizzle-discuss thread linked above.
<version> must then be either 7.1.x or 2012.01.x but not both.