To me, this is the same concern as with software development: you don't
    change a public API with every release of your library. Rather, you make

They don't seem the same to me.  Unlike API's, there are non-technical
reasons to change licenses.  

Anyway, I guess it'll be up to rms.  

k



Reply via email to