555 - Need a version-numbering scheme for bugzilla source.

Status: VERIFIED FIXED

(Bugzilla :: Bugzilla-General, defect, P2)

Description

[Terry Weissman]

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.

Comment 1

[Terry Weissman]

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.

Comment 2

[Terry Weissman]

I did this.

Comment 3

[Dave Miller [:justdave]]

verif. fixed and present in current source.  (a LONG time ago in a place far far 
away...)

Comment 4

[Dave Miller [:justdave]]

Moving to Bugzilla product