thisisnic commented on code in PR #14678:
URL: https://github.com/apache/arrow/pull/14678#discussion_r1034808763


##########
r/PACKAGING.md:
##########
@@ -0,0 +1,117 @@
+
+<!---
+  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 full documentation of the steps in this checklist, see the
+[Apache Arrow Release Management 
Guide](https://arrow.apache.org/docs/developers/release.html#post-release-tasks).
+
+- [ ] When a release candidate is created
+  [Create a GitHub issue](https://github.com/apache/arrow/issues/new/)
+  entitled `[R] CRAN release version X.X.X` and copy this checklist to the 
issue
+  
+- [ ] Confirm that all
+  [nightly tests and nightly packaging 
builds](https://lists.apache.org/[email protected]) are passing.
+- [ ] Check [current CRAN check 
results](https://cran.rstudio.org/web/checks/check_results_arrow.html)

Review Comment:
   Ah wait, patch releases originate from the initial release branch? We should 
document the difference in expectations here, I didn't know that.  In that 
case, I should expect that this commit is *not* in the branch as this is a 
patch release, right?
   
   I just checked the history for the 10.0.1 commit and it is there. Isn't the 
manual selection of which tickets go into a patch release already sorted (i.e. 
by Jacob/Raul) by the time we deal with the branch? So only if we wanted to 
release 10.0.1.1(i.e. some R-specific things) that we'd need to worry about 
that.



-- 
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