[RTEMS Project] #2886: RTEMS version is wrong on 4.11 branch

[RTEMS trac]

#2886: RTEMS version is wrong on 4.11 branch
-----------------------------+------------------------------
 Reporter:  Sebastian Huber  |       Owner:  Sebastian Huber
     Type:  defect           |      Status:  closed
 Priority:  normal           |   Milestone:  4.11.2
Component:  General          |     Version:  4.11
 Severity:  normal           |  Resolution:  wontfix
 Keywords:                   |
-----------------------------+------------------------------
Changes (by Chris Johns):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 I am going to close ticket this and have the 4.11 branch sit at 4.10.99.
 Anything built from git on the branch will be given "the branches" version
 number.

 It does mean the git source at the tag and "the release" tarball vary and
 the release script needs to update the version numbers in the source tree,
 which it already does, as part of cutting a release. Changing the process
 to make commits when tagging make the release procedure more complicated
 when dealing with release candidates or we end up with a whole bunch of
 release candidate commits to something and back again in-order to
 "correctly" tag a release.

 The other way of looking at this issue is to say the tag in the repo is
 the commit the release was based on and the release tarball is "the
 release" and nothing else is or can be that release. A suitable hash of
 the release tarball defines exactly "the release". This approach means the
 release scripts and repo are not touched during the release process,
 including release candidates, and this should make an audit of the what a
 release is simpler. The release scripts clearly define what is touched and
 that can be audited.

--
Ticket URL: <http://devel.rtems.org/ticket/2886#comment:4>
RTEMS Project <http://www.rtems.org/>
RTEMS Project