Fixed, but really really need to have an update system because right now
its hardcoded from installation, which is not always accurate.
** Changed in: aikiframework
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Aiki
Framework Admins, which is subscribed to aikiframework.
https://bugs.launchpad.net/bugs/912712
Title:
fix version number in the admin interface
Status in Aiki Framework:
Fix Released
Bug description:
The version number got scrapped with bassels' radical hacksaw. Bassel,
please fix this:
http://www.aikiframework.org/wiki/Aiki_Version_Conventions
The convention above is really sane, and can get the build number
with: bzr revnoT
Also, should check the last minor version number we were using and set
that.
This was set by the old make/build system in defs.inc
I reverted this file so this exists again. One option is to just pull
up the aiki revision number when you click on the revision number, so
it will pull up with more information about aiki in the admin
interface so we know where we are at.
What do you think about this?
In the past, had to run this with the build scripts:
bzr revno
So, the idea is remove the REVNO requirement in the define field, and
instead try to find this bazaar revno if it exists with:
bzr revno
If that command doesn't exist, then check
.bzr/branch/last-revision
If that doesn't exist, well, then shit, you aren't following our
development style which is to work from bazaar checkout.
Of course, for final releases, the version number should be set by
default in bootstrap.php as the version number
To manage notifications about this bug go to:
https://bugs.launchpad.net/aikiframework/+bug/912712/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~aikiframework.admins
Post to : [email protected]
Unsubscribe : https://launchpad.net/~aikiframework.admins
More help : https://help.launchpad.net/ListHelp
