[prev in list] [next in list] [prev in thread] [next in thread]
List: amarok-devel
Subject: Re: A proposal to release 2.9
From: Stefano Pettini <stefano.pettini () gmail ! com>
Date: 2018-02-24 22:58:44
Message-ID: CAJh1omQg3iiogzpQHVVd4SV+3G-9Se6nXgW_AVW0oFidye+uhg () mail ! gmail ! com
[Download RAW message or body]
Hi everybody,
it looks like there's a general agreement on releasing 2.9 from master,
Myriam is also fine with the plan. I said in the past I wanted to do it but
I have no experience and time so if Heiko can do it then I would prefer
this solution.
About KF5 and master, what's the plan? Merging the two, cherrypicking
patches since the fork or just abandoning master? I would not favor the
last solution as time was spent by many, including me, for useful fixes and
I would like to make sure that these are not lost (same reason why I
proposed to release 2.9).
It would be nice to fix the cover search, but this requires reviewing the
services available in 2018 and the license of their APIs. If none of the
services works, I would gray out the option on the menu.
Regards,
Stefano
On Wed, Feb 21, 2018 at 10:09 PM, Heiko Becker <heirecka@exherbo.org> wrote=
:
> Hello everybody,
>
> On 01/26/18 13:45, Mat=C4=9Bj Laitl wrote:
> > Hi Stefano,
> > I totally agree, 2.9 should be released to push the work done to users.
>
> I agree, although I don't really know how adoption by distros will turn
> out, considering Qt4 is EOL since quite some time, same for KDELibs
> (although not that long). But a release isn't that much effort and at
> least shows some activity and maybe provides incentive to contribute and
> if all that fails it's at least a fixed point before the port to Qt5/KF5.
>
> > I unfortunately won't find time to do it myself, but: try to start
> > making the release yourself! ;) It should be documented quite well.
>
> I'd be willing to tackle this, if nobody steps up (which appears to be
> the case at the moment, sorry if I stepped on any toes). Being a
> packager and having done a few extragear releases with releaseme should
> be quite helpful.
>
> So, I propose the following schedule:
>
> - 1 week to find out what can be fixed in short time with low manpower
> or should be disabled (e.g cover search services)
> - Create tarball afterward, give packagers and others some time to test
> - If all goes well release on March, 5th
> - Merge kf5 (which isn't unusable after the latest patches from Malte)
> into master afterwards
>
> > If you get stuck or need help with particular tasks, speak up on ML (an=
d
> > CC me), I'm quite confident somebody from us will help. (people usually
> > procrastinate "big" tasks, but answering a concrete questions is much
> > easier)
>
> What I'm a bit unsure about is how to communicate the release. Something
> along the lines "This release might not be as polished as past releases,
> but there's some activity and bug fixes, a port to KF5 and any help is
> certainly welcome."?
>
> Cheers,
> Heiko
>
> > On Wed, Jan 24, 2018 at 8:43 PM Stefano Pettini
> > <stefano.pettini@gmail.com <mailto:stefano.pettini@gmail.com>> wrote:
> >
> > Hi Matej,
> >
> > have you received my last message to the mailing list? What's your
> > opinion? Sadly the project seems really abandoned, still it doesn't
> > mean we can't do a last release. I also wrote to Myriam, she didn't
> > answer, hope everything is fine.
> >
> > Stefano
> >
> >
> > ---------- Forwarded message ----------
> > From: *Stefano Pettini* <stefano.pettini@gmail.com
> > <mailto:stefano.pettini@gmail.com>>
> > Date: Sun, Jan 7, 2018 at 10:05 AM
> > Subject: A proposal to release 2.9
> > To: amarok-devel@kde.org <mailto:amarok-devel@kde.org>
> >
> >
> > Hi,
> >
> > it's many years now that Amarok 2.9 is about to be released. The
> > saturday-morning emails remember us weekly that there are still a
> > couple of regressions since years. In the meanwhile development
> > almost stopped, but not completely. I, like many, contributed with
> > small but important patches (otherwise we would haven't dedicated
> > time to provide such fixes).
> >
> > I think it's fair if the work since 2.8 is not wasted and 2.9 is
> > released.
> >
> > Current regressions are minor bugs, the only annoying thing not
> > working anymore is the cover search. But it's not a newly-introduce=
d
> > regression, just the world changed and all the services used for
> > cover search become not available anymore. It's not a problem not
> > present in 2.8 that people would face when updating to 2.9. It's
> > already broken now.
> >
> > I would disable what doesn't work to not give false impressions,
> > removing the broken services from cover search, and release 2.9.
> > This would fix the access to wikipedia and other bugs we dedicated
> > time to.
> >
> > Cover search can be restored later, if developers find time to
> > dedicate to it and somebody reviews the available services and
> > select the suitable ones for the future Amarok.
> >
> > Regards,
> > Stefano
>
[Attachment #3 (text/html)]
<div dir="ltr"><div><div><div>Hi everybody,<br><br></div>it looks like there's a \
general agreement on releasing 2.9 from master, Myriam is also fine with the plan. I \
said in the past I wanted to do it but I have no experience and time so if Heiko can \
do it then I would prefer this solution.<br><br></div><div>About KF5 and master, \
what's the plan? Merging the two, cherrypicking patches since the fork or just \
abandoning master? I would not favor the last solution as time was spent by many, \
including me, for useful fixes and I would like to make sure that these are not lost \
(same reason why I proposed to release 2.9).<br></div><div><br></div>It would be nice \
to fix the cover search, but this requires reviewing the services available in 2018 \
and the license of their APIs. If none of the services works, I would gray out the \
option on the menu.<br><br></div>Regards,<br>Stefano<br></div><div \
class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 21, 2018 at 10:09 PM, \
Heiko Becker <span dir="ltr"><<a href="mailto:heirecka@exherbo.org" \
target="_blank">heirecka@exherbo.org</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">Hello everybody,<br> <span class=""><br>
On 01/26/18 13:45, Matěj Laitl wrote:<br>
> Hi Stefano,<br>
> I totally agree, 2.9 should be released to push the work done to users.<br>
<br>
</span>I agree, although I don't really know how adoption by distros will \
turn<br> out, considering Qt4 is EOL since quite some time, same for KDELibs<br>
(although not that long). But a release isn't that much effort and at<br>
least shows some activity and maybe provides incentive to contribute and<br>
if all that fails it's at least a fixed point before the port to Qt5/KF5.<br>
<span class=""><br>
> I unfortunately won't find time to do it myself, but: try to start<br>
> making the release yourself! ;) It should be documented quite well.<br>
<br>
</span>I'd be willing to tackle this, if nobody steps up (which appears to be<br>
the case at the moment, sorry if I stepped on any toes). Being a<br>
packager and having done a few extragear releases with releaseme should<br>
be quite helpful.<br>
<br>
So, I propose the following schedule:<br>
<br>
- 1 week to find out what can be fixed in short time with low manpower<br>
or should be disabled (e.g cover search services)<br>
- Create tarball afterward, give packagers and others some time to test<br>
- If all goes well release on March, 5th<br>
- Merge kf5 (which isn't unusable after the latest patches from Malte)<br>
into master afterwards<br>
<span class=""><br>
> If you get stuck or need help with particular tasks, speak up on ML (and<br>
> CC me), I'm quite confident somebody from us will help. (people usually<br>
> procrastinate "big" tasks, but answering a concrete questions is \
much<br> > easier)<br>
<br>
</span>What I'm a bit unsure about is how to communicate the release. \
Something<br> along the lines "This release might not be as polished as past \
releases,<br> but there's some activity and bug fixes, a port to KF5 and any help \
is<br> certainly welcome."?<br>
<br>
Cheers,<br>
Heiko<br>
<span class="im HOEnZb"><br>
> On Wed, Jan 24, 2018 at 8:43 PM Stefano Pettini<br>
</span><span class="im HOEnZb">> <<a \
href="mailto:stefano.pettini@gmail.com">stefano.pettini@gmail.com</a> <mailto:<a \
href="mailto:stefano.pettini@gmail.com">stefano.pettini@gmail.<wbr>com</a>>> \
wrote:<br> ><br>
> Hi Matej,<br>
><br>
> have you received my last message to the mailing list? What's \
your<br> > opinion? Sadly the project seems really abandoned, still it \
doesn't<br> > mean we can't do a last release. I also wrote to \
Myriam, she didn't<br> > answer, hope everything is fine.<br>
><br>
> Stefano<br>
><br>
><br>
> ---------- Forwarded message ----------<br>
</span><span class="im HOEnZb">> From: *Stefano Pettini* <<a \
href="mailto:stefano.pettini@gmail.com">stefano.pettini@gmail.com</a><br> > \
<mailto:<a href="mailto:stefano.pettini@gmail.com">stefano.pettini@gmail.<wbr>com</a>>><br>
> Date: Sun, Jan 7, 2018 at 10:05 AM<br>
> Subject: A proposal to release 2.9<br>
</span><div class="HOEnZb"><div class="h5">> To: <a \
href="mailto:amarok-devel@kde.org">amarok-devel@kde.org</a> <mailto:<a \
href="mailto:amarok-devel@kde.org">amarok-devel@kde.org</a>><br> ><br>
><br>
> Hi,<br>
><br>
> it's many years now that Amarok 2.9 is about to be released. The<br>
> saturday-morning emails remember us weekly that there are still a<br>
> couple of regressions since years. In the meanwhile development<br>
> almost stopped, but not completely. I, like many, contributed with<br>
> small but important patches (otherwise we would haven't dedicated<br>
> time to provide such fixes).<br>
><br>
> I think it's fair if the work since 2.8 is not wasted and 2.9 is<br>
> released.<br>
><br>
> Current regressions are minor bugs, the only annoying thing not<br>
> working anymore is the cover search. But it's not a \
newly-introduced<br> > regression, just the world changed and all the \
services used for<br> > cover search become not available anymore. It's \
not a problem not<br> > present in 2.8 that people would face when updating \
to 2.9. It's<br> > already broken now.<br>
><br>
> I would disable what doesn't work to not give false impressions,<br>
> removing the broken services from cover search, and release 2.9.<br>
> This would fix the access to wikipedia and other bugs we dedicated<br>
> time to.<br>
><br>
> Cover search can be restored later, if developers find time to<br>
> dedicate to it and somebody reviews the available services and<br>
> select the suitable ones for the future Amarok.<br>
><br>
> Regards,<br>
> Stefano<br>
</div></div></blockquote></div><br></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic