Thanks, Herman.
I'd like to suggest an alternative, more dynamic way of versioning Cinelerra. Instead of having patches committed in trunk and at some point (which is not described anywhere) do a 2.1.x release, what about using the Google Chrome/Chromium approach to have a fast pace versioning? Basically every time a patch is applied, there would be a version bump (maybe not immediate, but after some time of testing). This would help the user to understand what they are getting and in principle (by providing a clear way to get older versions) to fall back to previous ones. This method would also answer to my original question regarding the roadmap. Hence, this approach wouldn't need any short term roadmap, but instead new 2.1.x versions would go as stability releases. BTW, if I may, I'd like to suggest that links in the download page of the official cinelerra-CV website to the source of stable releases (2.1.5, now) to be separate from git, as it is now on the download page of Cinelerra-CV. This is *highly* confusing, since version 2.1.5 in git that I donwloaded 2 months ago is different than the same version 2.1.5 that I donwloaded today: being git, people have committed patches. So, like in most open-source projects, there should be links to stable releases (possibly using the approach above), and for the bravest, links to git (named, development branch, or nightly, whatever). Otherwise, the current situation is pretty confusing to the end user and for packagers like me. Nicola > To: [email protected] > Subject: Re: [CinCV] Cinelerra roadmap > From: [email protected] > Date: Tue, 15 Feb 2011 19:27:25 +0100 > > On Tue, 15 Feb 2011 06:03:46 +0100, Nicola Ferralis <[email protected]> > wrote: > > > In the past few weeks, there has been a very interesting discussion in this > > forum about the long term future of Cinelerra. This discussion made me > > wonder if a short-term roadmap of Cinelerra really exists. In particular I > > wonder if there is any set decision for a version 2.1.7 (and 2.1.8, 2.2, > > etc)? > > No, I don't think there is any off-list coordinated planning going on > to write a roadmap for the next release(s). Not yet, anyway. > > > I'd like to hear some thoughts about this. As the maintainer of the > > Cinelerra-ppa for Ubuntu, I wonder if instead of syncing only official > > releases, I should instead sync with git every time a commit is pushed. In > > this latter case, I would think a bump in version should be adopted. > > Good points for the agenda of the not-yet-scheduled developer meeting. :-) > > It's been too long since I wrote "what needs doing", without any progress > report or any meetings or published TODOs. Readers are getting impatient. > Not good. > > Why? Well, the webmistress got very busy with other film/video related > stuff, and I got occupied learning Cinelerra plugin programming, and > other unrelated stuff. Besides, it's winter up here. So there has been > too little worth reporting, but we're not dead yet. ;-) > > Anyhow, I don't feel _quite_ ready to lead a long march to a Next Gen > Cinelerra, yet. And I do think some firm and competent leadership would > be a Good Thing. I am ready to start scrathing my own itches, and fix > some other users' woes if they happen to be related to mine, as a start, > using the cinelerra.org DocuWiki as a kind of "blog" to tell about it. > > It's too early to say which wishes any of the coding contributors will > be able or willing to fulfill. I only promise that there will be _some_ > activity within the next few days. Best wishes! > > -- > Herman Robak > > _______________________________________________ > Cinelerra mailing list > [email protected] > https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
