paleolimbot commented on code in PR #14678: URL: https://github.com/apache/arrow/pull/14678#discussion_r1035040959
########## r/PACKAGING.md: ########## @@ -0,0 +1,129 @@ + +<!--- + Licensed to the Apache Software Foundation (ASF) under one + or more contributor license agreements. See the NOTICE file + distributed with this work for additional information + regarding copyright ownership. The ASF licenses this file + to you under the Apache License, Version 2.0 (the + "License"); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, + software distributed under the License is distributed on an + "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + KIND, either express or implied. See the License for the + specific language governing permissions and limitations + under the License. +--> + +# Packaging checklist for CRAN release + +For a high-level overview of the release process see the +[Apache Arrow Release Management Guide](https://arrow.apache.org/docs/developers/release.html#post-release-tasks). + +Before the release candidate is cut: + +- [ ] [Create a GitHub issue](https://github.com/apache/arrow/issues/new/) + entitled `[R] CRAN packaging checklist for version X.X.X` + and copy this checklist to the issue. +- [ ] Evaluate the status of any failing + [nightly tests and nightly packaging builds](https://lists.apache.org/[email protected]). These checks + replicate most of the checks that CRAN runs, so we need them all to be passing + or to understand that the failures will not result in a rejection from CRAN. Review Comment: You got it! The high-level intent is just that we want all the tests to pass in all the environments we care about, and ideally we want to fix any failures before the release candidate is cut. The bullet point further down where we create a draft PR and run `crossbow submit -g r` should ideally just be a formality...we don't want to reach that step and realize that we actually have to fix a bunch of problems. -- 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]
