[NeXus-definitions-tickets] [NeXusDefinitions] #212: set version number of release packages

[NeXus Base Classes and Instrument Definitions]

#212: set version number of release packages
-------------------------+------------------------------
 Reporter:  Pete Jemian  |      Owner:  Pete Jemian
     Type:  defect       |     Status:  new
 Priority:  major        |  Milestone:  release NXDL 1.0
Component:  general      |   Keywords:
-------------------------+------------------------------
 The version numbers are not consistent:

 * 3.1 The version as defined in nxdl.xsd, in targetNamespace and xmlns:nx
 (and used a lot)
 * 4.3.0  The version as defined CPackOptions.cmake.in (consistent with
 code release version)
 * 1.0 The TRAC server has this as the milestone. In README, a note says
 the next release (using Sphinx) will be 1.1.

 By using version 4.3.0, we sync the NXDL version number with the code
 release.  This is good.  To use version 4.3.0, we need to change the
 nxdl.xsd file and all related XML files and tools in both code and
 definitions that use this string.  That's a big job.  This may have
 additional consequences with other tools, such as NeXpy.

 To use version 1.0, same thing and choice is arbitrary (other than that
 this is first release).

 To use version 3.1, the only edit is in file CPackOptions.cmake.in.

 Recommend that the initial release of NXDL use version 3.1 since that
 appears in most files.  I'll check the manual to ensure this is used
 there, as well.  We can sync the version number with the code release in
 the next revision of NXDL.

-- 
Ticket URL: <http://trac.nexusformat.org/definitions/ticket/212>
NeXus Base Classes and Instrument Definitions <http://www.nexusformat.org/>
NeXus Base Classes and Instrument Definitions