-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Hannes,
thanks for pushing out the latest changes. If i remember correctly we have now merged nearly everything that was intended to be merged, except for one of Monty's alsa fixes, that caused serious playback problems for Hannes. So what do we still want to merge before releasing Cin2.1.5CV? (except for an update of the about page / version variable ;)) Personally speaking I would prefer a release rather soon for the following reasons: 1. a "new version" should encourage distributions to build new packages which should decrease the time that has to be spend for answering "where can i get (the latest) packages for XY" 2. a "new version" should encourage users to look for "new (old) bugs", hopefully resulting in new tickets on bugs.cinelerra.org. Adding a new version there makes it easier to keep track of what is still an issue. (I'm aware that many old bugs aren't fixed yet, but we won't fix them all in finite time, so waiting for all bugs being fixed would prohibit the release of > 2.1 forever ;-)) 3. a "new version" might encourage someone to contribute again some patches, as he/she sees that something is going on with cinelerra. (e.g. gentoo's patches weren't forwarded to our ML at some point as nothing happened) 4. releasing other bugfix releases (e.g. 2.1.6) should become "easier" to do when a first step is done. Hannes, Monty, Einar, what do you think? (as you've contributed most of the new patches) With best regards, Simeon On 11/04/10 21:08, Johannes Sixt wrote: > On Mittwoch, 3. November 2010, Simeon Völkel wrote: >> I've just reformatted Monty's three patches you hadn't committed yet due to >> their formatting. They are now available in my git repo, together with an >> extended commit message written my Monty. I hope you can merge them now >> into your repo, so that we get a step closer to the release of Cin2.1.5CV. > > Thanks, I appreciate it. > > I pushed out these patches, but I substituted Monty as author. (I hope you > don't mind.) nope, just wasn't aware of how to do that :) > > -- Hannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzTKmEACgkQph/voQkhF7wnswCgiMqOwHb4qG8q3Q0Tktqx46AK NcoAn35VTNpfweWfTefdsB8Gup9Vpkao =027Z -----END PGP SIGNATURE----- _______________________________________________ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
