[GRASS-dev] Re: [GRASS GIS] #587: svn versions should better
reflect svn rev
GRASS GIS
trac at osgeo.org
Wed Apr 13 08:13:04 EDT 2011
#587: svn versions should better reflect svn rev
--------------------------+-------------------------------------------------
Reporter: hamish | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 6.4.2
Component: Default | Version: svn-trunk
Resolution: | Keywords: g.version, configure
Platform: All | Cpu: All
--------------------------+-------------------------------------------------
Comment(by martinl):
Replying to [comment:60 hamish]:
> > It's not right, it's not redundant for final release at all. Currently
> > users have no information what is the revision of their build
(g.version,
> > wxGUI About window). It's common information which user could expect
to know.
>
> It's completely redundant for a tagged release. In that case the version
number of GRASS is all that is important and the svn version is simply an
unused development artifact, 100% documented if they care to look it up
(~10 sec in trac), but mostly irrelevant trivia to non-developers.
>
> I suppose someone with a random nightly build of 6.4.svn would not know
if they are before or after a point release, or someone just saw a "fixed
in stable branch r12345" and wanted to quickly know if their GRASS was
newer or older than that, but that's about it.
In one sentence: I can't see any point why user should not have access to
this information (in the case he/she is interested about that).
> > > The release branch must be tested when .svn/ dirs and svn CLI tools
are not
> > > present on the tarball/build machine. (in my quick tests last year I
just su
> > > renamed those temporarily in /usr/bin/, see earlier comments in the
ticket)
> > > It would not be nice to only discover a bug once the tarball was
released and
> > > a non-dev tried it.
> >
> > This feature has been introduced 17 months ago (r39622). Recently
backported to
> > devbr6 by you. What time is need to get finally this minor feature to
release? ;-)
>
> you miss my point. it has been tested in developers' svn builds, but
never outside of svn builds, which is what a point release is (svn
export). A beta1 or RC1 release is a suitable time to test that, so if you
want to take responsibility it, by all means go for backport now.
thanks, I can take this kind of responsibility, going to backport it.
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/587#comment:61>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list