From Newsgroup: muc.lists.freebsd.ports
------=_Part_878450_1977279969.1784639321734
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Hello FreeBSD Ports team,
We are working on preparing a new port for the FEATHER project and would like to confirm the recommended submission workflow before proceeding.
From the Porter's Handbook, we understand that Bugzilla is used for submitting new ports. However, I would like to clarify a couple of points:
- Is opening a Bugzilla issue with a link to the port repository sufficient for review, or is it expected that the submission also includes a patch/diff against the current Ports tree?
- If a Bugzilla submission is the correct approach, is there anything else you would recommend including to help a ports committer review and integrate the new port?
- Is there any preferred way to request a review from a ports committer once the Bugzilla submission is ready?
We would like to follow the preferred FreeBSD contribution workflow and make the review process as straightforward as possible.
Thank you for your time and guidance.
Best regards,
Paul Stanciuc
------=_Part_878450_1977279969.1784639321734
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<html><head></head><body><div class="ydp71184458yahoo-style-wrap" style="font-family:verdana, helvetica, sans-serif;font-size:13px;"><div dir="ltr" data-setdir="false"><div><p data-start="478" data-end="503" class="ydpff5f000bPDq2pG_selectionAnchorContainer">Hello FreeBSD Ports team,<span class="ydpff5f000bPDq2pG_selectionAnchor"></span></p>
<div dir="ltr" data-setdir="false">We are working on preparing a new port for the <strong data-start="550" data-end="561">FEATHER</strong> project and would like to confirm the recommended submission workflow before proceeding.</div>
<p data-start="652" data-end="793">From the Porter's Handbook, we understand that Bugzilla is used for submitting new ports. However, I would like to clarify a couple of points:</p>
<ol data-start="795" data-end="1259">
<li data-section-id="120s7u0" data-start="795" data-end="980">
Is opening a Bugzilla issue with a link to the port repository sufficient for review, or is it expected that the submission also includes a patch/diff against the current Ports tree?
</li>
<li data-section-id="sf4in6" data-start="981" data-end="1147">
If a Bugzilla submission is the correct approach, is there anything else you would recommend including to help a ports committer review and integrate the new port?
</li>
<li data-section-id="t9buic" data-start="1148" data-end="1259">
Is there any preferred way to request a review from a ports committer once the Bugzilla submission is ready?
</li>
</ol>
<p data-start="1261" data-end="1388">We would like to follow the preferred FreeBSD contribution workflow and make the review process as straightforward as possible.</p>
<p data-start="1390" data-end="1427">Thank you for your time and guidance.</p> <p data-start="1429" data-end="1442">Best regards,</p>
<p data-start="1444" data-end="1461"><strong data-start="1444" data-end="1461">Paul Stanciuc</strong></p></div><br></div></div></body></html>
------=_Part_878450_1977279969.1784639321734--
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to
news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2