Some information you might have missed.
Sparsecontent map does not build its extensions by default, and besides, I am doing regular releases so you should not need to bind to SNAPSHOTS and build your own, but I can understand why you might want maintain a fork.
There were release scripts that had been developed from version 0.1 through to 0.11 in tools did the releases, dealt with the fact that the release plugin will not release with any SNAPSHOT present, doesn't like timestamped snapshots in poms and the issue of generating and signing those timed snapshots as well as ensuring that all versions that should be rolled forward are rolled forward in the correct way. The maven release plugin doesnt work correctly with some of the OSGi bundles. The process was fully documented at https://confluence.sakaiproject.org/display/KERNDOC/Release+Procedure
It runs the integration tests which may be why you would not want to use it.
2 years ago I went down a simular route to where you are going now.
I suggest if you are not going to use those scripts, then you delete them, and go through KERNDOC edit any pages that document the release process and remove all references to them.
As always every new pathway is different so YMWV.