Hello Wes,
> As discussed last month I think we should aim for time-based releases. > I think a good release cadence for this project right now is > approximately every 2 months. So based on this a 0.13 release > candidate should be cut the week of March 18. This sounds fine. > I'll follow up on this thread every week or so with a status update > until we are in the 0.13 end-game. Note that there were a lot of > problems with the 0.12 release process -- what steps are we taking to > prevent those from happening again? I guess we are about to write some docker files. We could dockerize some of the release steps to ensure that they run in the same environment. One of the problems in releasing was always that the environment of the release manager was different from the environment of the previous one. Also we have seen various build issues that only occured in the release verification setups. We should aim to replicate some of the setups like "building arrow on various debian versions" in Docker and run the dockerfiles before we cut the RC. We could also run them as nightlies but I guess our build matrix gets too CPU-intensive when we run them each night. Uwe
