Hi,
Without any of this, people will just switch back to totem-xine or
other, non-GNOME apps like always, or just continue self-confirming that
Linux sucks. Very disappointing after my hard work to make GStreamer not
totally suck from an end user's point of view. Basically a total year
On Wed, 2006-01-18 at 12:44 -0700, Elijah Newren wrote:
So, here's my proposal:
Ship with 0.10. Have everything default to it. Also include 0.8 in
the ftp directory, but not used. Include a big old section in the
release notes explaining the situation and letting people know that
they can
On 1/18/06, Elijah Newren [EMAIL PROTECTED] wrote:
On 1/15/06, Vincent Untz [EMAIL PROTECTED] wrote:
Hi all,
So, the release team messed up and didn't keep close enough tabs on
everything, resulting in discovering an issue pretty late. We need to
try to find rough consensus in the
On 1/19/06, Bob Kashani [EMAIL PROTECTED] wrote:
The transmogrify script/patch fails during build with the following
error:
Did you run autogen.sh after running the transmogrify script?
Works for me, when also using autogen...
___
desktop-devel-list
On Thu, 2006-01-19 at 13:09 -0700, Elijah Newren wrote:
On 1/19/06, Bob Kashani [EMAIL PROTECTED] wrote:
The transmogrify script/patch fails during build with the following
error:
Did you run autogen.sh after running the transmogrify script?
Works for me, when also using autogen...
On Thu, 2006-01-19 at 10:44 -0700, Elijah Newren wrote:
Okay, so this is now official; Gstreamer 0.10 is the plan for Gnome
2.14. There's only one minor change to my proposal above, namely that
instead of adding unsed 0.8 tarballs to ftp just refer to them in the
important notice in the
On Thu, 2006-01-19 at 12:52 -0800, Bob Kashani wrote:
On Thu, 2006-01-19 at 13:09 -0700, Elijah Newren wrote:
On 1/19/06, Bob Kashani [EMAIL PROTECTED] wrote:
The transmogrify script/patch fails during build with the following
error:
Did you run autogen.sh after running the
On 1/19/06, Bob Kashani [EMAIL PROTECTED] wrote:
On Thu, 2006-01-19 at 12:52 -0800, Bob Kashani wrote:
On Thu, 2006-01-19 at 13:09 -0700, Elijah Newren wrote:
On 1/19/06, Bob Kashani [EMAIL PROTECTED] wrote:
The transmogrify script/patch fails during build with the following
error:
On 1/19/06, Elijah Newren [EMAIL PROTECTED] wrote:
Appears to be an errant 'm' character at the very beginning of
gnome-media-2.13.6/grecord/src/gsr-window.c... any chance we could
get an updated tarball with that fixed?
I hope I didn't step on any toes or do anything inappropriate but
since
On Mon, 2006-01-16 at 16:14 -0500, Luis Villa wrote:
JWZ is an ass, and has been for a long time. If forced to take the
admittedly unpleasant choice between overwhelming maintainers so that
they never look at bugzilla at all, or incorrectly closing bugs which
might be reopened later, we
On 1/15/06, Vincent Untz [EMAIL PROTECTED] wrote:
Hi all,
So, the release team messed up and didn't keep close enough tabs on
everything, resulting in discovering an issue pretty late. We need to
try to find rough consensus in the community.
So, here's my understanding of this thread and the
On Wed, 2006-01-18 at 00:22 +1100, Jeff Waugh wrote:
Is GNOME 2.10 maintained?
The way things are, that's almost equivalent to asking whether any
distributions with long-running support commitments ever shipped GNOME
2.10. We already discussed this once:
On Wed, 2006-01-18 at 14:06 -0500, Luis Villa wrote:
His tantrum was on our extremely irresponsible transition from 1.x to
2.0, where no one bothered to see if there were regressions, we didn't
provide a migration path for user's settings, we didn't write migration
documents for all the
quote who=Federico Mena Quintero
We need to mock, ridicule, and ostracise distributions which don't commit
their patches for non-HEAD versions of GNOME to CVS.
I will get the rubber chicken.
A while back, someone mentioned they had a script that polled for patches in
various distro packages
ons, 18,.01.2006 kl. 12.44 -0700, skrev Elijah Newren:
On 1/15/06, Vincent Untz [EMAIL PROTECTED] wrote:
Hi all,
So, the release team messed up and didn't keep close enough tabs on
everything, resulting in discovering an issue pretty late. We need to
try to find rough consensus in the
Hi Vincent,
On Mon, 2006-01-16 at 22:42 +0100, Vincent Untz wrote:
Well, the question is: is GStreamer 0.8 totally unmaintained?
Yup.
I had
understood that Ronald was planning to make a new release with some
fixes, so that's why I proposed to not close the bugs.
I don't know what Ronald's
Le mardi 17 janvier 2006 à 10:48 +0100, Andy Wingo a écrit :
Hi Vincent,
On Mon, 2006-01-16 at 22:42 +0100, Vincent Untz wrote:
Well, the question is: is GStreamer 0.8 totally unmaintained?
Yup.
Thanks for all the people running deployed software running Gstreamer
0.8 :(
--
Frederic
quote who=Frederic Crozat
Le mardi 17 janvier 2006 à 10:48 +0100, Andy Wingo a écrit :
Hi Vincent,
On Mon, 2006-01-16 at 22:42 +0100, Vincent Untz wrote:
Well, the question is: is GStreamer 0.8 totally unmaintained?
Yup.
Thanks for all the people running deployed software
On Tue, 2006-01-17 at 08:00 -0500, Frederic Crozat
[EMAIL PROTECTED] wrote:
Le mardi 17 janvier 2006 10:48 +0100, Andy Wingo a crit :
On Mon, 2006-01-16 at 22:42 +0100, Vincent Untz wrote:
Well, the question is: is GStreamer 0.8 totally unmaintained?
Yup.
Thanks for all the people
ons, 18,.01.2006 kl. 00.22 +1100, skrev Jeff Waugh:
quote who=Frederic Crozat
Le mardi 17 janvier 2006 à 10:48 +0100, Andy Wingo a écrit :
Hi Vincent,
On Mon, 2006-01-16 at 22:42 +0100, Vincent Untz wrote:
Well, the question is: is GStreamer 0.8 totally unmaintained?
Yup.
Le mercredi 18 janvier 2006 à 00:22 +1100, Jeff Waugh a écrit :
quote who=Frederic Crozat
Le mardi 17 janvier 2006 à 10:48 +0100, Andy Wingo a écrit :
Hi Vincent,
On Mon, 2006-01-16 at 22:42 +0100, Vincent Untz wrote:
Well, the question is: is GStreamer 0.8 totally unmaintained?
Hi,
Is GNOME 2.10 maintained?
If you want to do an analogy, you should ask : is GNOME 2.12
maintained ? ;)
No - since GNOME 2.14 is not out yet.
The question is - is GNOME maintaining more than one stable branch at
any point ?
After discussing on irc, it seems not everybody has the
Vincent/Glynn:
On Mon, 2006-01-16 at 07:28 +0100, Vincent Untz wrote:
+ quite a few people were assuming that 0.10 was the plan for 2.14 and
were totally unaware that 0.8 had even been on the plan. Ubuntu and
Fedora development versions (i.e. the distros that Elijah checked or
found
Hey,
On Mon, 2006-01-16 at 07:28 +0100, Vincent Untz wrote:
+ quite a few people were assuming that 0.10 was the plan for 2.14 and
were totally unaware that 0.8 had even been on the plan. Ubuntu and
Fedora development versions (i.e. the distros that Elijah checked or
found out
Hi,
Well Tim is working on just fixing Totem and gnome-media for 0.10
and will continue to do so for the next months at the minimum. Up to now
his progress have been slow due to having to port over plugins for 0.8
as part of his porting effort, but now that this is mostly taken care of
he can
On Mon, 2006-01-16 at 11:59 +0100, Christian Fredrik Kalager Schaller
wrote:
Hi,
Well Tim is working on just fixing Totem and gnome-media for 0.10
and will continue to do so for the next months at the minimum. Up to now
his progress have been slow due to having to port over plugins for 0.8
as
On Mon, 2006-01-16 at 11:27 +, Bastien Nocera wrote:
The problem is that the stuff that used to work doesn't anymore.
Well stuff that used to cause crashes in 0.8 doesn't anymore, so it goes
both ways.
And there are over 80 opened bugs against the Totem GStreamer backend,
most of them
Hi Christian,
Le lundi 16 janvier 2006 à 14:45 +0100, Christian Fredrik Kalager
Schaller a écrit :
And there are over 80 opened bugs against the Totem GStreamer backend,
most of them should be either fixed in Totem, reassigned to GStreamer,
or put on NEEDINFO (against 20 for the xine-lib
Hi,
Of those 80 most are from the 0.8 days. And they illustrate the problem
with nobody working on the 0.8 stuff anymore.
So, can we hope that some of you (Tim?)
Let's not shovel too much dirt on Tim yet :) We're already passing him
all of the hot potatoes. Tim's focusing on the 0.10
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
Le lundi 16 janvier 2006 à 21:07 +0100, Thomas Vander Stichele a écrit :
Hi,
Of those 80 most are from the 0.8 days. And they illustrate the problem
with nobody working on the 0.8 stuff anymore.
So, can we hope that some of you (Tim?)
Let's not shovel too much dirt on Tim yet
On Mon, 2006-01-16 at 21:04 +0100, Vincent Untz wrote:
And there are over 80 opened bugs against the Totem GStreamer backend,
most of them should be either fixed in Totem, reassigned to GStreamer,
or put on NEEDINFO (against 20 for the xine-lib backend).
Of those 80 most are from
Hi Vincent,
So the dual 0.8/0.10 thing for gnome-media has been discussed and our
opinion was that we didn't want Tim to waste time working on a dual
backend system when he already had a lot on his plate.
Personally I think we should make 2.13 releases using 0.10. If the
release team decide that
They could use basic triaging in the sense that someone should go
through them and see what applies to the 0.10 version. I think that
you'd find most GStreamer bug triagers to mark them as obsolete if they
apply only to the 0.8 backend though, and I don't know if that's what
you want
On 1/16/06, Vincent Untz [EMAIL PROTECTED] wrote:
They could use basic triaging in the sense that someone should go
through them and see what applies to the 0.10 version. I think that
you'd find most GStreamer bug triagers to mark them as obsolete if they
apply only to the 0.8 backend
Le lundi 16 janvier 2006 à 21:44 +0100, Christian Fredrik Kalager
Schaller a écrit :
Hi Vincent,
So the dual 0.8/0.10 thing for gnome-media has been discussed and our
opinion was that we didn't want Tim to waste time working on a dual
backend system when he already had a lot on his plate.
On 1/16/06, Elijah Newren [EMAIL PROTECTED] wrote:
On 1/16/06, Vincent Untz [EMAIL PROTECTED] wrote:
They could use basic triaging in the sense that someone should go
through them and see what applies to the 0.10 version. I think that
you'd find most GStreamer bug triagers to mark them
On 1/16/06, Elijah Newren [EMAIL PROTECTED] wrote:
See http://blogs.gnome.org/view/newren/2005/09/30/0 for more details
where I'm coming from, but I'm basically going to disagree with
Vincent here -- I think it should be perfectly fine to mark all those
bugs as obsolete and tell the reporter
Le lundi 16 janvier 2006 à 13:52 -0700, Elijah Newren a écrit :
On 1/16/06, Vincent Untz [EMAIL PROTECTED] wrote:
They could use basic triaging in the sense that someone should go
through them and see what applies to the 0.10 version. I think that
you'd find most GStreamer bug
Hi,
Well, if all other changes that have been done/will be done in 2.13 are
only fixes that can go in 2.12, then I guess it's okay.
Thomas also proposed to add a patch for GStreamer 0.10 support in CVS
and a configure switch that would apply the patch.
My proposal was slightly different;
Hi all,
So, the release team messed up and didn't keep close enough tabs on
everything, resulting in discovering an issue pretty late. We need to
try to find rough consensus in the community.
Some background on the problem:
+ http://live.gnome.org/TwoPointThirteen_2fDesktop (and the jhbuild
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.
42 matches
Mail list logo
