--===============1854260497791083118== Content-Type: multipart/alternative; boundary=047d7b10c98dfd48d904dc454b84 --047d7b10c98dfd48d904dc454b84 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, May 9, 2013 at 10:27 AM, Mat=C4=9Bj Laitl wrote: > On 8.=E2=80=AF5.=E2=80=AF2013 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 crash= y > > 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 t= o > 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). --=20 Mark Kretschmann Amarok Developer Fellow of the Free Software Foundation Europe http://amarok.kde.org - http://fsfe.org --047d7b10c98dfd48d904dc454b84 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Thu, May 9, 2013 at 10:27 AM, Mat=C4=9Bj Laitl <matej@lai= tl.cz> wrote:
On 8.=E2=80=AF5.=E2=80=AF2013 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 cras= hy
> 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 h= ave
changed a couple of strings (and we don't have dual stable/trunk transl= ations
set up).

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.

The Kubuntu devs were very quick, t= hey've already built packages containing this patch (currently in testi= ng). 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 onl= y need to release this for Linux (does not affect Windows, AFAICS).

--
Mark Kretschmann
Amarok Dev= eloper
Fellow of the Free Software Foundation Europe
http://amarok.kde.org - http://fsfe.org
--047d7b10c98dfd48d904dc454b84-- --===============1854260497791083118== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Amarok-devel mailing list Amarok-devel@kde.org https://mail.kde.org/mailman/listinfo/amarok-devel --===============1854260497791083118==--