2 After some discussion on IRC, I think it's time to propose a
3 formal plan for the next 6 months or so to the list.
5 I think most people are in agreement that we need a period of time
6 in which we can focus on improving non-core bits (like elements,
7 schedulers, autopluggers, applications, etc.) In the last cycle,
8 there was a lot of time spent with a significant number of plugins
9 broken, and it's realistic to assume that this could happen again
10 in a 0.9 unstable series.
14 - We continue to develop the 0.8.x series as HEAD, with the obvious
15 requirement that all changes be ABI/API compatible.
17 - API additions are encouraged, as long as they are well-thought-out.
19 - Significant API additions should be developed on a separate branch
20 (not HEAD) to test out any bugs.
22 In mid-August (or so, in order to coordinate with GNOME-2.8), we have
25 - Continue with 0.8.x releases, obviously ABI compatible with 0.8.0.
27 - or, remove deprecated functions, readjust the padding on structures,
28 perhaps make a few additional ABI changes [1], and quickly go to
31 I prefer the latter, although we don't have to decide that until
32 later. In either case, there should be no API changes that affect
33 more than a bare minimum of elements or applications.
35 A few things that we won't be able to do without a true unstable
38 - using GstStructure for all GstEvents.
40 - significant clock changes
42 - significant scheduling changes
44 - separation of headers into application and plugin headers
46 - anything that requires modification of every plugin
48 There are perils with having HEAD being the stable branch,
49 specifically that bugs can creep in and accidentally cause regressions
50 in releases. I'm hoping that the introduction of media regression
51 testing and also the development of new testsuites will keep this
52 to a minimum. Don't forget that accidental bugs that get into
53 releases typically cause rude IRC conversations, which we really
54 don't need. Please keep the bugs (and the rudeness) to a minimum.
56 Also, keep in mind that we will have to live with 0.8's unfixable
57 bugs for an entire year.[2]
64 [1] I'm thinking about making GstData a subclass of GTypeInstance or
66 [2] But then, 0.6 was 1 year ago, and felt a lot more buggy when it
71 -------------------------------------------------------
72 This SF.Net email is sponsored by: IBM Linux Tutorials
73 Free Linux tutorial presented by Daniel Robbins, President and CEO of
74 GenToo technologies. Learn everything from fundamentals to system
75 administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
76 _______________________________________________
77 gstreamer-devel mailing list
78 gstreamer-devel@lists.sourceforge.net
79 https://lists.sourceforge.net/lists/listinfo/gstreamer-devel