From amarok-devel Fri Feb 14 12:22:46 2020 From: Myriam Schweingruber Date: Fri, 14 Feb 2020 12:22:46 +0000 To: amarok-devel Subject: Re: Help with code revision process Message-Id: X-MARC-Message: https://marc.info/?l=amarok-devel&m=158168299008697 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--0000000000000b4d90059e884446" --0000000000000b4d90059e884446 Content-Type: text/plain; charset="UTF-8" Hi Pedro, On Fri, 14 Feb 2020 at 13:12, Pedro de Carvalho Gomes < pedrogomes81@gmail.com> wrote: > Hi, > > Yesterday I created three Review Requests. However only one of them has an > associated bugtrack ID. > Thanks a lot for these. Did you check the bug database if those are related to existing bugs? If yes it should be easy to add the ID to close the bugs on commit, but it is not a hard requirement > And none has an associated Phabricator task. Are these required for the > review process? > No, not a hard requirement either. > What's the usual procedure to submit a PR? > You did quite well AFAICS, now we need somebody to review the code. FWIW: it's always good to test build to avoid breaking it o commit -- Proud member of the Amarok and KDE Community Protect your freedom and support the work of the FSFE: http://www.fsfe.org Please don't send me proprietary file formats, use ISO standard ODF instead (ISO/IEC 26300) --0000000000000b4d90059e884446 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Pedro,

On Fri, 14 Feb 2020 at = 13:12, Pedro de Carvalho Gomes <pedrogomes81@gmail.com> wrote:
Hi,

Yesterday I created th= ree Review Requests. However only one of them has an associated bugtrack ID= .

Thanks a lot for these. Did you= check the bug database if those are related to existing bugs? If yes it sh= ould be easy to add the ID to close the bugs on commit, but it is not a har= d requirement
=C2=A0
And none has an associated Phabricator tas= k. Are these required for the review process?

No, not a hard requirement either.
What's the = usual procedure to submit a PR?

=
You did quite well AFAICS, now we need somebody to review the code.=C2= =A0

FWIW: it's always good to test build to avoid = breaking it o commit
=C2=A0

--
<= div>
Proud member of th= e Amarok and KDE Community
Protect your freedom and support the work=C2=A0of the=C2=A0FSFE:
http://www.fsfe.org
Please don't send= me proprietary file formats,
use ISO standard ODF instead (ISO/I= EC 26300)
--0000000000000b4d90059e884446--