Re: [certi-dev] Problem with assignPHVPSToRequest

[Eric Noulard]

2010/11/10 Michael Raab <address@hidden>:
>> Nice catch too.
> This one was hard to find. Maybe you should think about inserting bugs into
> CERTI that are more obvious. :-)
>
>> Probably some other people do but with 3.3.3.
>> If you look at the diff between 3.3.3 and forthcoming 3.4.0 you'll see the
>> gap :-]
> Sorry, I do not understand what you mean.

I mean that many users still use CERTI 3.3.3 because CERTI 3.4.0 is not out,
and many user do not "cvs checkout".

The gap between 3.3.3 and 3.4.0 is now huge :-]
(big rework on the internal message framework in order to be able
 to generate ALL internal messages used by CERTI)

CERTI 3.3.3 it does not contain this bug :-]

Since our test suite is obviously too small we did not capture this bug.
Thus we need:
    1) a better test suite
    2) a greater involvement  of our user in order to beta test
         unreleased version just as you currently does.

That way we will get a rock-solid CERTI release.

>> That said thank you for your quest.
>> I've just checked in that fix (and the previous the one for NULL Tag on
>> UAV and SI just before that).
>> Now I will do similar changes for 1516 version too.
> Fine, thanks.
>
> Btw, do you plan to switch from CVS to are more current versioning system 
> like SVN?

Currently no, but I would rather personnally switch to git and not to SVN.
I may start a separate thread discussion on this subject,
in fact it would be some "restart" see
http://lists.nongnu.org/archive/html/certi-devel/2009-06/msg00002.html

Do you have any issue with cvs ?
Does the pserver access worry you?

You may already have access to git clone of certi and certi application tree:
http://mapserver.flightgear.org/git/?p=certi;a=summary
http://mapserver.flightgear.org/git/?p=certi-apps;a=summary

those are read-only but they may be useful.

-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org