Re: GStreamer version for 2.14
- From: Luis Villa <luis villa gmail com>
- To: Elijah Newren <newren gmail com>
- Cc: Vincent Untz <vuntz gnome org>, desktop-devel-list gnome org
- Subject: Re: GStreamer version for 2.14
- Date: Mon, 16 Jan 2006 16:01:52 -0500
On 1/16/06, Elijah Newren <newren gmail com> wrote:
> On 1/16/06, Vincent Untz <vuntz gnome org> 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 though, and I don't know if that's what
> > > you want in this case.
> >
> > I don't think marking them as obsolete is okay right now. I'd use the
> > status whiteboard so we can easily know they're only happening with the
> > 0.8 backend. (Or maybe create a gstreamer0.8 component, but this is
> > ugly).
>
> 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 they are free to reopen if they
> experience the same issue under 0.10. I think which versions are
> considered obsolete ought to be up to the maintainers (though we'd
> appreciate a note in the product specific guidelines, linked to from
> the browse page in bugzilla, so that triagers can help). There is a
> tradeoff that needs to be made and we don't want to be too agressive
> just closing out 'old' bugs, but I think we tend to err far on the
> side off keeping too many bugs open that just aren't helpful.
This is basically the case we created obsolete for (as opposed to
wontfix) so while it isn't perfect, I'm generally in agreement with
Elijah here.
Luis
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]