[GRASS-dev] Can we release 6.2.3?
Markus Neteler
neteler at fbk.eu
Sun Nov 18 12:27:54 EST 2007
On Sun, Nov 18, 2007 at 03:10:18PM +0100, Moritz Lennert wrote:
> On Sun, November 18, 2007 15:05, Markus Neteler wrote:
> > On Sun, Nov 18, 2007 at 11:42:45AM +0100, Moritz Lennert wrote:
> >> On Fri, November 16, 2007 23:20, Markus Neteler wrote:
> >> > Due to the list migrations I lost track on the 6.2.3 backports.
> >> > Are there pressing outstanding things?
> >> > http://grass.gdf-hannover.de/wiki/GRASS_6.2_Feature_Plan#6.2.3cvs
> >> > looks good to me.
> >> > Objections to release 6.2.3 on Monday?
> >>
> >> No idea if the bugs listed there were the only once corrected since 6.2.
> >> Would it make sense to systematically check the changelog in HEAD since
> >> the date of release of 6.2.2 to see if there are other things that need
> >> updating ? Has this been done already ? Is this too much work ?
> >
> > It would be very good to check since the 6.2.2 release.
>
> I don't know what the correct cvs command for that is.
It is (in the release branch):
CVSBRANCH=`cat CVS/Entries | grep AUTHORS | cut -d'/' -f6 | cut -b2-`
echo $CVSBRANCH
#version:
MAJOR=`cat include/VERSION | head -1 | tail -1`
MINOR=`cat include/VERSION | head -2 | tail -1`
RELEASE=`cat include/VERSION | head -3 | tail -1`
VERSION=${MAJOR}.${MINOR}.${RELEASE}
echo $VERSION
#create ChangeLog on release branch:
sh tools/cvs2cl.pl --follow "$CVSBRANCH"
mv ChangeLog ChangeLog_$VERSION
Markus
More information about the grass-dev
mailing list