If you haven't already, you may need to re-create the 3.0.1 version in JIRA. I deleted it this week (along with 2.0.1) while doing some prep for 4.0.0 since it seemed like we weren't going to be doing a patch release given the proximity of the next major release. Apologies if that was a mistake.
Neal On Fri, Mar 12, 2021 at 7:19 AM Andy Grove <andygrov...@gmail.com> wrote: > Thanks for the reviews and edits so far on this. It looks like we have a > process defined that should work well. I will create a PR to add this > documentation to the repo this weekend and will create the release-rust-3.0 > branch and start cherry-picking 3.0.1 bug fixes into that branch. If anyone > has any bug fixes that they would like to see in 3.0.1 please tag them in > JIRA by adding 3.0.1 to the fix version. > > Thanks, > > Andy. > > On Thu, Mar 11, 2021 at 9:05 AM Andy Grove <andygrov...@gmail.com> wrote: > > > Now that we have the ability to vote on source releases for patch > > releases, with each implementation having more freedom to release outside > > of the major release process, we need to document how to do this for the > > Rust implementation (and this is probably of interest to other > > implementations as well since we probably want to be fairly consistent > > about this process). > > > > I have created a JIRA [1] started a Google doc for us to collaborate on > > this [2] > > > > I'm sure we have at least one bug fix that is a candidate for a 3.0.1 > > release so I propose that we tag these in JIRA and make a patch release > > soon to try this process out. I am happy to do the bulk of the work on > this. > > > > Thanks, > > > > Andy. > > > > [1] https://issues.apache.org/jira/browse/ARROW-11934 > > [2] > > > https://docs.google.com/document/d/1i2Elk6J0H4nhPeQZdLDyqvHoRbsabx2iOTXLHxxNqRE/edit?usp=sharing > > >
