[GRASS5] Branching for 5.0.0 ahead

[Helena]

Markus, did you get and submitted the new r.sun from Jaro? It should be much
better than the old one.

May I ask somebody to run the latest submitted s.surf.rst with your data to
make sure that
we did not break anything when adding the anisotropy? We tested it, but it
would be useful
to have somebody run it independently (you do not have to test the anisotropy
option as
that is a very special case, but just make sure that you are getting the same
results as before
with some "standard" run).

And if somebody really is bored could you also run v.surf.rst and
r.resamp.rst to double check
that they are working (although this is not critical as these two programs
are not used too often).

The cutting planes still crash nviz, but I did not have time to get the data
to Glynn, but this
is not a critical bug as it works most of the time and also  most people do
not use cutting planes.
A note should be included into NVIZ manual.

Helena

Bernhard Reiter wrote:

> As self-appointed release assistant
> (nobody ever commented on me doing this)
> I remind you that our plan is to create the release branch this week.
>
> Thus this is your last chance to speak up that you still need
> more hours to check in your stuff.
>
> Do not start big additions to grass5 head branch
> without asking on the list.
>
> Work in progress that I've noticed:
>         - d.zoom        Radim
>         - m.in.e00      Michel
>         - proj          Roger
>
> Please finish as soon as you can and let us know.
> If you cannot finish this within the next days,
> we might have to back the changes out and delay them to later releases.
>
> As for the procedure:
>         Markus, as GRASS project coodinator
>         can you work with Glynn to actually create the Release branch?
>         Glynn, you have done quite some coding lately on GRASS
>         and you know a lot about CVS. Thus it would be great,
>         if you could assist Markus here.
>
>         You both have to make sure that the release branch only contains
>         useful code we want to release and that you know is stable.
>
>   ------------------------------------------------------------------------
>    Part 1.2Type: application/pgp-signature