bullet03 commented on a change in pull request #17089:
URL: https://github.com/apache/beam/pull/17089#discussion_r833174274



##########
File path: website/www/site/content/en/contribute/_index.md
##########
@@ -285,12 +335,15 @@ export GOLANG_PROTOBUF_REGISTRATION_CONFLICT=ignore
    
jobs](https://cwiki.apache.org/confluence/display/BEAM/Contribution+Testing+Guide#ContributionTestingGuide-Pre-commit).
 If a test fails and appears unrelated to your
    change, you can cause tests to be re-run by adding a single line comment on 
your
    PR

Review comment:
       done

##########
File path: website/www/site/content/en/contribute/_index.md
##########
@@ -303,7 +356,7 @@ export GOLANG_PROTOBUF_REGISTRATION_CONFLICT=ignore
 1. If you don't get any response in 3 business days, email the [dev@ mailing 
list](/community/contact-us) to ask for someone to look at your pull
    request.
 
-### Make the reviewer's job easier
+#### Make the reviewer's job easier

Review comment:
       done

##########
File path: website/www/site/content/en/contribute/_index.md
##########
@@ -303,7 +356,7 @@ export GOLANG_PROTOBUF_REGISTRATION_CONFLICT=ignore
 1. If you don't get any response in 3 business days, email the [dev@ mailing 
list](/community/contact-us) to ask for someone to look at your pull

Review comment:
       done

##########
File path: website/www/site/content/en/contribute/_index.md
##########
@@ -321,69 +374,38 @@ export GOLANG_PROTOBUF_REGISTRATION_CONFLICT=ignore
    all commits in the PR during merge, however if a PR has a mixture of 
independent changes that should not be squashed, and fixup commits,
    then the PR author should help squashing fixup commits to maintain a clean 
commit history.
 
-</div>
-
-## When will my change show up in an Apache Beam release?
+#### Apache Beam Releases
 
 Apache Beam makes minor releases every 6 weeks. Apache Beam has a
 
[calendar](https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com)
 for
 cutting the next release branch. Your change needs to be checked into master 
before the release branch is cut
 to make the next release.
 
-## Stale pull requests
+#### Stale pull requests

Review comment:
       done




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to