Hello,
as discussed last month in the thread "Using git for openvas development" we
came to the conclusion that it already helps a lot fot the git-svn users
if we just separate out the openvas-plugins module into a SVN repository of its
own. This also reduces noise for the commit mailing list.
So here is the plan we need to finally confirm:
1. Create a new SVN Repository "openvas-nvts" and integrate it on Wald
properly with its own commit mailing list "openvas-nvts-commits".
2. Coordinate a date of switch among developers where no commits to
openvas-plugins should happen. Probably it is a very short time window.
3. Copy over the content of openvas-plugins/ into the new repository.
Note: The new repo will not have "trunk/branches/tags" as it is not relevant
for the NVT development.
4. Remove (svn remove) the openvas-plugins/ directory from openvas repository.
This also means to not copy over the SVN history to the new repo (by copying the
repo). I thunk this creates more trouble than good.
Anything to add to this plan?
Any last concerns or doubts?
If the plan is generally not disagreed by the end of this week, I will take
care
of step 1 and start the separation.
All the best
Jan
--
Dr. Jan-Oliver Wagner | ++49-541-335084-0 | http://www.greenbone.net/
Greenbone Networks GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B
202460
Geschäftsführer: Lukas Grunwald, Dr. Jan-Oliver Wagner
_______________________________________________
Openvas-devel mailing list
Openvas-devel@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-devel
