Hi Richard, If you, or some one else, is happy to take ownership of configuration control, then please feel free to run with it. That would be much appreciated.
I have too many other responsibilities to take on any extra work in this area, and am content with codec2-dev and SVN to support my development activities. I'm happy to answer any questions about where code is at, roadmaps etc to support the person responsible for configuration control. However I still feel the core issue is finding some one who will actually take long term, week in, week out, responsibility and make this happen. Thanks, David On 01/08/15 11:58, Richard Shaw wrote: > On Fri, Jul 31, 2015 at 5:36 PM, David Rowe <[email protected] > <mailto:[email protected]>> wrote: > > Hi Richard, > > Core issue for me is lack of people actually cutting code on this > project. > > So before we add another layer of effort/process, is there anyone who > will step up and take ownership of this area? > > > I don't think it will cause too much pain, I'm thinking a layout like: > > codec2/ > codec2/branches > codec2/tags > codec2/trunk > > codec2/trunk would be analogous to codec2-dev. > > Where we are with 0.98 beta (codec2 0.4) would be a branch: > > codec2/branches/0.4 > > When were happy with it, it would get tagged to a release: > > codec2/tags/0.4 (optionally 0.4.0) > > And then I could tar.gz up the source and we can make it available on > freedv.org <http://freedv.org>. > > Thoughts? > > Thanks, > Richard > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > Freetel-codec2 mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/freetel-codec2 > ------------------------------------------------------------------------------ _______________________________________________ Freetel-codec2 mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freetel-codec2
