Le lundi 16 janvier 2006 à 07:34 +0100, Vincent Untz a écrit : > Le lundi 16 janvier 2006 à 07:28 +0100, Vincent Untz a écrit : > > It is possible to have both 0.8 and 0.10 installed at the same time, so > > the decision could be to ship both and have modules use 0.10 if it works > > for them and otherwise use 0.8. Or maybe support both with a configure > > switch. However, either of these would mean taking a lot of developer > > time that would seem much better spent fixing a single version. > > > > It is somewhat unfortunate, but the lateness of the issue will probably > > force some difficulty in the schedule. We may need to shove > > feature/module freeze effectively back a week (but not doing the same > > for subsequent dates) or being lenient with GStreamer-related freeze > > break requests at first to get this straightened out. > > My personal opinion is that we should keep the schedule as it is right > now, but accept some changes related to GStreamer so we can try to have > 0.10 for 2.14. If it doesn't work well enough (one month before the > big .0 release, eg), then we'll be able to go back to 0.8.
Answering myself to try to move the discussion here (instead of the thread on release-team). Here's a more detailed "plan" I propose: + keep compatibility with both 0.8 and 0.10 in all of our modules + push to fix regressions in 0.10 + come back in ~1 month (on February 13th, when tarballs for 2.14.0 Beta 2 are due) and look at what has been fixed and see if the worst bugs reported against our modules are for GStreamer 0.8 or GStreamer 0.10. I'm not sure, but I don't think there are features in the various modules using GStreamer that *require* 0.10, are there? Vincent -- Les gens heureux ne sont pas pressés. _______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list