Hi,
we are almost there with 1.0.0 of NessusClient.
But currently it looks like we will have yet another
RC release ...
However, there are some comprehensive new features in
our queue that should lead to 1.2.0.
It would be very helpful if we could manage these
in the CVS. This could only be done if a branch
for the stable 1.0 series is created (then new stuff
could go into HEAD).
Renaud, would it be OK to create the 1.0-branch already
now allthough we are still in RC-phase?
Best
Jan
--
Jan-Oliver Wagner: www.intevation.de/~jan | GISpatcher: www.gispatcher.de
Kolab Konsortium : www.kolab-konsortium.de | Thuban : thuban.intevation.org
Intevation GmbH : www.intevation.de | Kolab : www.kolab.org
FreeGIS : www.freegis.org | GAV : www.grass-verein.de
_______________________________________________
Nessus-devel mailing list
Nessus-devel@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus-devel
we are almost there with 1.0.0 of NessusClient.
But currently it looks like we will have yet another
RC release ...
However, there are some comprehensive new features in
our queue that should lead to 1.2.0.
It would be very helpful if we could manage these
in the CVS. This could only be done if a branch
for the stable 1.0 series is created (then new stuff
could go into HEAD).
Renaud, would it be OK to create the 1.0-branch already
now allthough we are still in RC-phase?
Best
Jan
--
Jan-Oliver Wagner: www.intevation.de/~jan | GISpatcher: www.gispatcher.de
Kolab Konsortium : www.kolab-konsortium.de | Thuban : thuban.intevation.org
Intevation GmbH : www.intevation.de | Kolab : www.kolab.org
FreeGIS : www.freegis.org | GAV : www.grass-verein.de
_______________________________________________
Nessus-devel mailing list
Nessus-devel@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus-devel