Bug 1271 - Xorg 6.8 release canidate identifies itself as "6.7" after the build is complete
Summary: Xorg 6.8 release canidate identifies itself as "6.7" after the build is complete
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: * Other (show other bugs)
Version: git
Hardware: All Linux (All)
: high minor
Assignee: Kevin E. Martin
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 351
  Show dependency tree / graph
 
Reported: 2004-09-01 15:43 UTC by Roland Mainz
Modified: 2011-10-15 15:49 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Roland Mainz 2004-09-01 15:43:06 UTC 
Xorg 6.8 release canidate still identifies itself as "6.7" after the build is
complete.

Steps to reproduce:
1. Pull source
2. Build it:
% make World

Result:
Last lines of the builds are:
-- snip --
make[5]: Leaving directory
`/home/gismobile/projects/xorg/new_work001/xc/doc/hardcopy/XPRINT'
make[4]: Leaving directory
`/home/gismobile/projects/xorg/new_work001/xc/doc/hardcopy'
make[3]: Leaving directory `/home/gismobile/projects/xorg/new_work001/xc/doc'
make[2]: Leaving directory `/home/gismobile/projects/xorg/new_work001/xc'
make[1]: Leaving directory `/home/gismobile/projects/xorg/new_work001/xc'

Thu Sep  2 00:38:06 CEST 2004

Full build of Release 6.7 complete.
-- snip --

Expected result:
-- snip --
...

Full build of Release 6.8 complete.
-- snip --
Comment 1 Kevin E. Martin 2004-09-01 19:11:59 UTC 
This is known (Mike Harris pointed it out a few weeks ago).  It will be changed
when the final version number is set to 6.8.  Right now we are still on the
release candidates, which are 6.7.99.90x, so the 6.7 build is technically correct.

I will keep this open until the final version numbers have been changed. 
Assigning this one to myself.
Comment 2 Kevin E. Martin 2004-10-04 07:16:05 UTC 
The version number in the build was bumped before the release.
Closing.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.