For anyone interested this is the document that resulted from the Release Retrospective
https://docs.google.com/document/d/1xnCWpEqznzcMu3meWUk4SZnFlEiw1dRfh249T1dMXfg/edit# On Tue, Feb 1, 2022 at 11:30 PM Ian Joiner <iajoiner...@gmail.com> wrote: > Could you please share the retro board so that we can all comment on the > issues? > > I’m very sorry for at least two of the redos were actually related to ORC > with one of them caused by a simple import error I didn’t find in my Python > docker tests which is caused by the fact that my old way to run PyArrow dev > locally somehow broke around the 5.0.0 release. To prevent similar issues > from happening I will keep asking questions here until my local env > problems get fully resolved and both local tests and release verification > work for the languages I develop in. > > I will try to attend the usual Biweekly meeting tomorrow. > > Ian > > > On Feb 1, 2022, at 9:23 AM, Alessandro Molina < > alessan...@ursacomputing.com> wrote: > > > > For anyone interested on the topic, I got some feedbacks that suggest it > > might be more effective to have a meeting dedicated to the topic with the > > people who have been involved in preparing the release and subsequently > > share the outcome of that meeting with everyone at the Arrow biweekly > > meeting. > > > > Thus if you are interested in hearing about the release topic, feel free > to > > just join the usual Arrow Biweekly Meeting. The "post-mortem" will be > > shared and discussed at that meeting too. The meeting that I shared will > be > > focused on producing the post-mortem together with those who have been > > involved in preparing release 7.0.0 itself so that it can then be > discussed > > at the biweekly. > > > > On Tue, Feb 1, 2022 at 11:20 AM Alessandro Molina < > > alessan...@ursacomputing.com> wrote: > > > >> Given the unexpected amount of tries we had to go through to publish > >> version 7 (I don't think there were past cases where RC10 was reached), > it > >> would be helpful to go through what happened, what didn't work and what > we > >> can do to prevent it from happening again in the future. > >> > >> I created a meeting for tomorrow at 16:30 CET (15:30 UTC) that anyone is > >> welcome to join to follow or participate in the discussion. The meeting > >> link is at https://meet.google.com/jzg-gzks-qas > >> > >> After the meeting is completed I'll share a Google Docs with the notes > of > >> the meeting to make everyone aware of the outcome and what solutions > have > >> been proposed. > >> > >> Bests, > >> Alessandro > >> > >
