roadmap
Locked
 
|
hi,
i just start to understand the whole concept of gstreamer, but already has a few questions: - why there is not any kind of roadmap on the website? it's be useful if users and developers can know what's the current status, and what will be in the future and about when. even if deadlines are changing it still better than nothing. eg. what will be in 0.10, 0.11 or when will be 1.0 how many release will be in 0.10.x. etc? - why the gstreamer modules are not in sync in version number? ie. bad and base why not bot 0.10.15 or at least the same? how we can know which version fit to which version? otherwise how we can know when an element move from bad to good or ugly etc. imho it'd be even better to release eg gst-ffmpeg 0.10.15 if there is nothing change to be in sync with other plugins then users have to collect the right version for their software. eg if i use only good and not bad (so i don't download, install etc it) but it's turn out that i need bad too, than i need to somehow research which version of bad fit to my version of good etc.. just my 2c. yours. -- Levente "Si vis pacem para bellum!" ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
|
|
On Tue, 2008-01-22 at 00:20 +0100, Farkas Levente wrote:
> - why there is not any kind of roadmap on the website? it's be useful if > users and developers can know what's the current status, and what will > be in the future and about when. even if deadlines are changing it still > better than nothing. eg. what will be in 0.10, 0.11 or when will be 1.0 > how many release will be in 0.10.x. etc? That's mostly because we don't really know. Last I checked the plan was to continue with 0.10.x and the current API and ABI as long as it makes sense to do so. > - why the gstreamer modules are not in sync in version number? ie. bad > and base why not bot 0.10.15 or at least the same? Because they are released at different times with varying frequency (e.g. core+base are released much more often than, say, gst-plugins-bad or gst-ffmpeg). > how we can know which version fit to which version? otherwise how we > can know when an element move from bad to good or ugly etc. imho it'd > be even better to release eg gst-ffmpeg 0.10.15 if there is nothing > change to be in sync with other plugins then users have to collect the > right version for their software. eg if i use only good and not bad > (so i don't download, install etc it) but it's turn out that i need > bad too, than i need to somehow research which version of bad fit to > my version of good etc.. just my 2c. yours. Just get the latest release of each module. Gaps in the version number would be confusing too IMHO. Cheers -Tim ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
|
|
Tim Müller wrote:
> On Tue, 2008-01-22 at 00:20 +0100, Farkas Levente wrote: > >> - why there is not any kind of roadmap on the website? it's be useful if >> users and developers can know what's the current status, and what will >> be in the future and about when. even if deadlines are changing it still >> better than nothing. eg. what will be in 0.10, 0.11 or when will be 1.0 >> how many release will be in 0.10.x. etc? > > That's mostly because we don't really know. Last I checked the plan was > to continue with 0.10.x and the current API and ABI as long as it makes > sense to do so. imho roadmap are not so rigid but still give us some light of the directions. >> - why the gstreamer modules are not in sync in version number? ie. bad >> and base why not bot 0.10.15 or at least the same? > > Because they are released at different times with varying frequency > (e.g. core+base are released much more often than, say, gst-plugins-bad > or gst-ffmpeg). > >> how we can know which version fit to which version? otherwise how we >> can know when an element move from bad to good or ugly etc. imho it'd >> be even better to release eg gst-ffmpeg 0.10.15 if there is nothing >> change to be in sync with other plugins then users have to collect the >> right version for their software. eg if i use only good and not bad >> (so i don't download, install etc it) but it's turn out that i need >> bad too, than i need to somehow research which version of bad fit to >> my version of good etc.. just my 2c. yours. > > Just get the latest release of each module. Gaps in the version number > would be confusing too IMHO. sometimes it's not possible to use the latest version! eg the given version working, test and used in a real environment which is more critical than playing my music files, etc. i understand the above, BUT it's the same situation as eg: with gnome or kde when there is a new release of gnome than all subpackages has the same version. even if nothing changed in gnome-audio it's still has a new version in order to be able to recognized even later which version belong to which version. there is not any gap in version since each subpackage has always the same version. to translate it to gst: suppose that the current version is gst-core 0.10.15 but i still use gst-core 0.10.5 and i want to select the right version of gst-bad. who can i know that? -- Levente "Si vis pacem para bellum!" ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
|
|
Hi,
Farkas Levente schrieb: > Tim Müller wrote: >> On Tue, 2008-01-22 at 00:20 +0100, Farkas Levente wrote: >> >>> - why there is not any kind of roadmap on the website? it's be useful if >>> users and developers can know what's the current status, and what will >>> be in the future and about when. even if deadlines are changing it still >>> better than nothing. eg. what will be in 0.10, 0.11 or when will be 1.0 >>> how many release will be in 0.10.x. etc? >> That's mostly because we don't really know. Last I checked the plan was >> to continue with 0.10.x and the current API and ABI as long as it makes >> sense to do so. > > imho roadmap are not so rigid but still give us some light of the > directions. Yes sometimes it would be nice to know what each developer is working on and what is comming. > >>> - why the gstreamer modules are not in sync in version number? ie. bad >>> and base why not bot 0.10.15 or at least the same? >> Because they are released at different times with varying frequency >> (e.g. core+base are released much more often than, say, gst-plugins-bad >> or gst-ffmpeg). >> >>> how we can know which version fit to which version? otherwise how we >>> can know when an element move from bad to good or ugly etc. imho it'd >>> be even better to release eg gst-ffmpeg 0.10.15 if there is nothing >>> change to be in sync with other plugins then users have to collect the >>> right version for their software. eg if i use only good and not bad >>> (so i don't download, install etc it) but it's turn out that i need >>> bad too, than i need to somehow research which version of bad fit to >>> my version of good etc.. just my 2c. yours. >> Just get the latest release of each module. Gaps in the version number >> would be confusing too IMHO. > > sometimes it's not possible to use the latest version! eg the given > version working, test and used in a real environment which is more > critical than playing my music files, etc. > i understand the above, BUT it's the same situation as eg: with gnome or > kde when there is a new release of gnome than all subpackages has the > same version. even if nothing changed in gnome-audio it's still has a > new version in order to be able to recognized even later which version > belong to which version. there is not any gap in version since each > subpackage has always the same version. > to translate it to gst: suppose that the current version is gst-core > 0.10.15 but i still use gst-core 0.10.5 and i want to select the right > version of gst-bad. who can i know that? > We manage dependencies. If you want to upgrade gst-plugins-bad, it will tell you if your core or base is too old. The other way around it should be no problem, as we are in API stable mode for the whole 0.10 series. So there is no *right* version of bad matching core. Its usually the newer, the better. Stefan ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
|
|
In reply to this post by Farkas Levente-2
On Jan 22, 2008 1:01 PM, Farkas Levente <[hidden email]> wrote:
> Tim Müller wrote: > > On Tue, 2008-01-22 at 00:20 +0100, Farkas Levente wrote: > > > >> - why there is not any kind of roadmap on the website? it's be useful if > >> users and developers can know what's the current status, and what will > >> be in the future and about when. even if deadlines are changing it still > >> better than nothing. eg. what will be in 0.10, 0.11 or when will be 1.0 > >> how many release will be in 0.10.x. etc? > > > > That's mostly because we don't really know. Last I checked the plan was > > to continue with 0.10.x and the current API and ABI as long as it makes > > sense to do so. > > imho roadmap are not so rigid but still give us some light of the > directions. I agree completely. Where's the wiki?! I remember seeing it but I can't find it from anywhere. For me at least there are some interesting things happening like the parser base class and parser elements that would make decoders easier to write. There's also playbin2 (is it mainstream already?), the gst-ffmpeg update and the new gst-opengl module. And of course gst-openmax ;) > >> - why the gstreamer modules are not in sync in version number? ie. bad > >> and base why not bot 0.10.15 or at least the same? > > > > Because they are released at different times with varying frequency > > (e.g. core+base are released much more often than, say, gst-plugins-bad > > or gst-ffmpeg). > > > >> how we can know which version fit to which version? otherwise how we > >> can know when an element move from bad to good or ugly etc. imho it'd > >> be even better to release eg gst-ffmpeg 0.10.15 if there is nothing > >> change to be in sync with other plugins then users have to collect the > >> right version for their software. eg if i use only good and not bad > >> (so i don't download, install etc it) but it's turn out that i need > >> bad too, than i need to somehow research which version of bad fit to > >> my version of good etc.. just my 2c. yours. > > > > Just get the latest release of each module. Gaps in the version number > > would be confusing too IMHO. > > sometimes it's not possible to use the latest version! eg the given > version working, test and used in a real environment which is more > critical than playing my music files, etc. > i understand the above, BUT it's the same situation as eg: with gnome or > kde when there is a new release of gnome than all subpackages has the > same version. even if nothing changed in gnome-audio it's still has a > new version in order to be able to recognized even later which version > belong to which version. there is not any gap in version since each > subpackage has always the same version. > to translate it to gst: suppose that the current version is gst-core > 0.10.15 but i still use gst-core 0.10.5 and i want to select the right > version of gst-bad. who can i know that? Not all the packages are updated. For example GLib and GTK releases happen just in time for the GNOME release but the versions are different. The version numbers are not the same because if for some reason GLib decides to update twice or not at all it wouldn't matter for GNOME because of the backwards binary compatibility. The same happens with GStreamer core and subcomponents. Welcome to the GStreamer community :) -- Felipe Contreras ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
|
|
Felipe Contreras schrieb:
> On Jan 22, 2008 1:01 PM, Farkas Levente <[hidden email]> wrote: >> Tim Müller wrote: >>> On Tue, 2008-01-22 at 00:20 +0100, Farkas Levente wrote: >>> >>>> - why there is not any kind of roadmap on the website? it's be useful if >>>> users and developers can know what's the current status, and what will >>>> be in the future and about when. even if deadlines are changing it still >>>> better than nothing. eg. what will be in 0.10, 0.11 or when will be 1.0 >>>> how many release will be in 0.10.x. etc? >>> That's mostly because we don't really know. Last I checked the plan was >>> to continue with 0.10.x and the current API and ABI as long as it makes >>> sense to do so. >> imho roadmap are not so rigid but still give us some light of the >> directions. > > I agree completely. Where's the wiki?! I remember seeing it but I > can't find it from anywhere. > http://gstreamer.freedesktop.org/wiki/ > > For me at least there are some interesting things happening like the > parser base class and parser elements that would make decoders easier > to write. There's also playbin2 (is it mainstream already?), the > gst-ffmpeg update and the new gst-opengl module. > > And of course gst-openmax ;) > Difficult thing is to come up with a plan how to do the roadmap. Lots of things are developed by submitting patches to bugzilla. The need review, discussion and then they can hopefully be included (once there is agreement). But if everyone starts listing patches there, I doubt it would help. Then there is ad-hoc activity schduled on irc. Someone notices something and starts checking. Eventually others help and so on. Also every developer has areas where there is some continuos improvment. But its hard to tell in advance what can be added/improved/fixed next. Stefan ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
«
Return to GStreamer-devel
|
1 view|%1 views
| Free forum by Nabble | Edit this page |