Re: [fltk.development] FLTK version number update and release process [WAS: Re: [fltk.bugs] [MOD] STR #2932: 1.3.2 tarball not packaged properly]

2013-03-01 Thread MacArthur, Ian (Selex ES, UK)
1) For large commercial software, I have a VERSION file in the main directory with a single line in it: VERSION=#.# This can be include'ed from Makefiles to define macros used on everything from compile lines to Makefile construction

Re: [fltk.development] FLTK version number update and release process [WAS: Re: [fltk.bugs] [MOD] STR #2932: 1.3.2 tarball not packaged properly]

2013-03-01 Thread Peter Åstrand
On Fri, 1 Mar 2013, MacArthur, Ian (Selex ES, UK) wrote: Oh, and another question: WHEN do we upgrade the version number(s)? (a) immediately after one release, for the next release, or What Mike said: As soon as *anything* in SVN changes after a release, we need to bump the version

[fltk.development] FLTK version number update and release process [WAS: Re: [fltk.bugs] [MOD] STR #2932: 1.3.2 tarball not packaged properly]

2013-02-28 Thread Albrecht Schlosser
On 01.03.2013 01:04, Greg Ercolano wrote: On 02/28/13 15:24, Albrecht Schlosser wrote: We'll need to take care of this for the next release. Unfortunately there are several places with version numbers that need to be adjusted manually for each release. :-( We probably should have a