Closed
Bug 555
Opened 26 years ago
Closed 26 years ago
Need a version-numbering scheme for bugzilla source.
Categories
(Bugzilla :: Bugzilla-General, defect, P2)
Tracking
()
VERIFIED
FIXED
Bugzilla old
People
(Reporter: terry, Assigned: terry)
References
Details
I think I should introduce a version number in the bugzilla source, and
make tarballs.
My current thoughts are:
- Create a file called "version.tcl", which contains simply a line like
set versionnumber "1.4"
- Make the version number appear in the header or something.
- Whenever I feel it's time to spin a new tarball, I'll up the version number,
create the tarball, and then UP THE NUMBER AGAIN. That way, the running
version will always have a different version number than the one in the
tarball. So, I can still check in changes whenever I feel like it, and not
worry that my thing is different than something out there wrapped in a
tarball.
Assignee | ||
Comment 1•26 years ago
|
||
The database is being reorganized a bit. Instead of the Bugzilla product,
a new Webtools product has been created, with Bugzilla being a component of it.
This bug is being moved from the old Bugzilla product to the new Webtools
product.
Assignee | ||
Updated•26 years ago
|
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 2•26 years ago
|
||
I did this.
Comment 3•24 years ago
|
||
verif. fixed and present in current source. (a LONG time ago in a place far far
away...)
Status: RESOLVED → VERIFIED
Comment 4•23 years ago
|
||
Moving to Bugzilla product
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
QA Contact: matty
Target Milestone: --- → Bugzilla old
Version: other → unspecified
Updated•12 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•