Thanks for having contacted me, it makes sense indeed not to duplicate
efforts or undertake divergent paths.
Actually what me and the others maintainers of the debian ardour
package thought, was to not make a separate package out of ardour 2.0,
but upload its beta releases into experimental till when the final
stable version comes out, and then upload it to unstable.
That's because according to our experience sessions created with
ardour .99 load fine with ardour 2.0, even though we can't of course
exclude bugs.
If there was a way to safely import the .99-generated sessions into
2.0, would be there still others reasons to make two separate
packages?
Ciao,
Free