#23563: document changes files release-readiness requirement in doc/HACKING --------------------------------+------------------------------------ Reporter: catalyst | Owner: (none) Type: task | Status: needs_revision Priority: Medium | Milestone: Tor: 0.3.2.x-final Component: Core Tor/Tor | Version: Severity: Normal | Resolution: Keywords: tor-doc tor-releng | Actual Points: Parent ID: #23562 | Points: Reviewer: | Sponsor: --------------------------------+------------------------------------ Changes (by catalyst):
* status: needs_review => needs_revision Comment: Mostly looks good; thanks! I would suggest adding a sentence or two in HowToReview.md and possibly also CodingStandards.md about trying to conform to the changes file writing style that release engineers will apply in II.1.2 of ReleasingTor.md. (That way we can hopefully get reviewers and patch authors to help take more text writing/editing load off of the release engineers.) -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/23563#comment:3> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs