[prev in list] [next in list] [prev in thread] [next in thread] 

List:       amarok-devel
Subject:    Re: [amarok] src/context/engines/wikipedia: Fix crashes on track change (both with Phonon-GStreamer
From:       Mark Kretschmann <kretschmann () kde ! org>
Date:       2013-05-09 9:01:32
Message-ID: CAGzDjiN4eOH=7kH7AMhFM=-NYF29i2x6EZrDtjPqDpzYQZ8twg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Thu, May 9, 2013 at 10:27 AM, Matěj Laitl <matej@laitl.cz> wrote:

> On 8. 5. 2013 Erik Hovland wrote:
> > > We might want to do a 2.7.1 release for Linux, with this patch.
> >
> > May I second this sentiment. Amarok 2.7.0 on Ubuntu 13.04 is very crashy
> > because of this issue. It would be very helpful to get this tagged and
> get
> > it into backports or updates.
>
> We certainly can, OTOH, I wouldn't like to tag the current master as 2.7.1,
> because it contains other commits that need to settle down and because we
> have
> changed a couple of strings (and we don't have dual stable/trunk
> translations
> set up).
>
> What we can do is to create another branch on top of v2.7.0 and just add a
> couple of unobtrusive bugfix commits. We also can just remind packagers to
> apply these patches without a release, they already patch Amarok anyway.
>

The Kubuntu devs were very quick, they've already built packages containing
this patch (currently in testing). Still, I think doing a real bugfix
release is cleaner than relying on the packagers to patch things.

I suggest we go with a new branch from 2.7.0 and cherry-pick a couple of
important bugfixes, then tag as 2.7.1. We only need to release this for
Linux (does not affect Windows, AFAICS).

-- 
Mark Kretschmann
Amarok Developer
Fellow of the Free Software Foundation Europe
http://amarok.kde.org - http://fsfe.org

[Attachment #5 (text/html)]

<div dir="ltr">On Thu, May 9, 2013 at 10:27 AM, Matěj Laitl <span \
dir="ltr">&lt;<a href="mailto:matej@laitl.cz" \
target="_blank">matej@laitl.cz</a>&gt;</span> wrote:<br><div \
class="gmail_extra"><div class="gmail_quote"><blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
 <div class="im">On 8. 5. 2013 Erik Hovland wrote:<br>
&gt; &gt; We might want to do a 2.7.1 release for Linux, with this \
patch.<br> &gt;<br>
&gt; May I second this sentiment. Amarok 2.7.0 on Ubuntu 13.04 is very \
crashy<br> &gt; because of this issue. It would be very helpful to get this \
tagged and get<br> &gt; it into backports or updates.<br>
<br>
</div>We certainly can, OTOH, I wouldn&#39;t like to tag the current master \
as 2.7.1,<br> because it contains other commits that need to settle down \
and because we have<br> changed a couple of strings (and we don&#39;t have \
dual stable/trunk translations<br> set up).<br>
<br>
What we can do is to create another branch on top of v2.7.0 and just add \
a<br> couple of unobtrusive bugfix commits. We also can just remind \
packagers to<br> apply these patches without a release, they already patch \
Amarok anyway.<br></blockquote></div><div><br></div><div>The Kubuntu devs \
were very quick, they&#39;ve already built packages containing this patch \
(currently in testing). Still, I think doing a real bugfix release is \
cleaner than relying on the packagers to patch things.</div> <div \
style><br></div><div style>I suggest we go with a new branch from 2.7.0 and \
cherry-pick a couple of important bugfixes, then tag as 2.7.1. We only need \
to release this for Linux (does not affect Windows, AFAICS).</div> <div \
style><br></div>-- <br><div dir="ltr">Mark Kretschmann<br>Amarok \
Developer<br>Fellow of the Free Software Foundation Europe<br><a \
href="http://amarok.kde.org" target="_blank">http://amarok.kde.org</a> - <a \
href="http://fsfe.org" target="_blank">http://fsfe.org</a></div>

</div></div>



_______________________________________________
Amarok-devel mailing list
Amarok-devel@kde.org
https://mail.kde.org/mailman/listinfo/amarok-devel


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic