[GRASS-dev] Re: [GRASS GIS] #392: backport G_is_c_null_value() to devbr6

Markus Neteler neteler at osgeo.org
Thu Dec 18 02:42:52 EST 2008


On Wed, Dec 17, 2008 at 9:11 PM, Paul Kelly
<paul-grass at stjohnspoint.co.uk> wrote:
>> #392: backport G_is_c_null_value() to devbr6
>>
>> Comment (by hamish):
>>  For rc2, to completely replace null_val.c or not? I am still a bit unsure-
>>  is there actually a bug in the current devbr6 version or is the idea to
>>  keep the methods in sync to ease future maintenance?

Since there are no comments there does not seem to be a bug
in GRASS 6.x.
So: if it ain't broken, don't fix it.

> Just a little comment about I'm not sure about the logic of intentionally
> planning to change a release candidate. To me, "release candidate" implies
> "this might be identical to the final release if we don't find any last
> minute bugs". If we're intentionally planning another change before the
> release it isn't really a release candidate after all.

I agree. But apparently the problem isn't there and we can now
create the release branch.

Markus


More information about the grass-dev mailing list