[prev in list] [next in list] [prev in thread] [next in thread]
List: fedora-devel-list
Subject: =?UTF-8?B?UmU6IFNlbGYgSW50cm9kdWN0aW9uOlPDtnJlbiBNw7ZsbGVy?=
From: Soeren Moeller <soerenmoeller2001 () gmail ! com>
Date: 2015-06-19 19:34:06
Message-ID: CA+Wk_LGzqnDYVVzSmp7wC5tC4j2O2OshdKMJ28yazFCJGZp0Tg () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Thank you for the relevant information, much appreciated.
2015-06-18 19:55 GMT+02:00 Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>:
>
> On Thu, Jun 18, 2015 at 05:27:22PM +0200, Soeren Moeller wrote:
> > I will try to comment on package reviews of other packages during the
next
> > few days, to get a feeling for the review process.
> Welcome!
>
> http://fedoraproject.org/PackageReviewStatus might be useful if you're
looking
> for review tickets. You'd want the "new tickets" subcategory... and start
> at the bottom, with the newest ones, and ignore green ones.
>
I now have done a review comment, carrying out most of the items from the
review guidelines on the orocos-bfl library:
https://bugzilla.redhat.com/show_bug.cgi?id=1233240
> If you want to concentrate on scientific packages, you might want to add
> yourself to CC list on
https://bugzilla.redhat.com/show_bug.cgi?id=FE-SCITECH,
> and also look at current list of dependent tickets.
Very interesting, I have but myself in cc and will use this as a starting
point for doing more review comments in the next days.
>
> You mentioned rpmlint, but not fedora-review. I strongly suggest it, since
> it does more interesting checks.
I used fedora-review for the review comment on orocos-bfl, thank you for
pointing it out. It is extremely effective in generating most of the files
I wanted to look at and a nice overview and list of points to start out
with.
Best
Sören
[Attachment #5 (text/html)]
<div dir="ltr">Thank you for the relevant information, much \
appreciated.<br><br>2015-06-18 19:55 GMT+02:00 Zbigniew Jędrzejewski-Szmek <<a \
href="mailto:zbyszek@in.waw.pl">zbyszek@in.waw.pl</a>>:<br>><br>> On Thu, \
Jun 18, 2015 at 05:27:22PM +0200, Soeren Moeller wrote:<br><br>> > I will try \
to comment on package reviews of other packages during the next<br>> > few \
days, to get a feeling for the review process.<br>> Welcome!<br>><br>> <a \
href="http://fedoraproject.org/PackageReviewStatus">http://fedoraproject.org/PackageReviewStatus</a> \
might be useful if you're looking<br>> for review tickets. You'd want the \
"new tickets" subcategory... and start<br>> at the bottom, with the \
newest ones, and ignore green ones.<br>><br>I now have done a review comment, \
carrying out most of the items from the review guidelines on the orocos-bfl \
library:<br><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1233240">https://bugzilla.redhat.com/show_bug.cgi?id=1233240</a><br><br>> \
If you want to concentrate on scientific packages, you might want to add<br>> \
yourself to CC list on <a \
href="https://bugzilla.redhat.com/show_bug.cgi?id=FE-SCITECH">https://bugzilla.redhat.com/show_bug.cgi?id=FE-SCITECH</a>,<br>> \
and also look at current list of dependent tickets.<br><br>Very interesting, I have \
but myself in cc and will use this as a starting point for doing more review comments \
in the next days.<br> <br>><br>> You mentioned rpmlint, but not fedora-review. \
I strongly suggest it, since<br>> it does more interesting checks.<br><br>I used \
fedora-review for the review comment on orocos-bfl, thank you for pointing it out. It \
is extremely effective in generating most of the files I wanted to look at and a nice \
overview and list of points to start out with.<br><br>Best<br>Sören<br><br></div>
[Attachment #6 (text/plain)]
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic