Thanks Krisztian for the update and all your work on this. We need a PMC member to step up to be the release manager for 0.10. Ideally they should undertake one or more dry runs of simulating the 0.10 release so we aren't faced with any surprises when we go to cut the release on ~July 23.
I moved the release management guide to Confluence: https://cwiki.apache.org/confluence/display/ARROW/Release+Management+Guide so we should ensure that there aren't any snowflake-y / undocumented aspects to the release build workflow. - Wes On Wed, Jul 11, 2018 at 11:54 AM, Krisztián Szűcs <szucs.kriszt...@gmail.com> wrote: > Hi All! > > Just want to send a quick summary about the packaging. > What's working: > python wheel builds > > conda package builds (the recent conda forge changes caused some unexpected > problems) > > linux package builds (enriched with ubuntu bionic) > > scheduled daily builds (triggered by travis) > > query build statuses from the CLI (see output https://bit.ly/2ztnSqV > (https://link.getmailspring.com/link/1531321550.local-b501f335-6185-v1.2.2-96fb3...@getmailspring.com/0?redirect=https%3A%2F%2Fbit.ly%2F2ztnSqV&recipient=ZGV2QGFycm93LmFwYWNoZS5vcmc%3D)) > > download and gpg sign the binary artifacts > > What's partially working: > binary artifact uploading (most of them are uploaded though) > > We have package name collisions due to uploading multiple tasks' artifacts to > a single github release > (see for example: https://github.com/kszucs/crossbow/releases/tag/build-160 > (https://link.getmailspring.com/link/1531321550.local-b501f335-6185-v1.2.2-96fb3...@getmailspring.com/1?redirect=https%3A%2F%2Fgithub.com%2Fkszucs%2Fcrossbow%2Freleases%2Ftag%2Fbuild-160&recipient=ZGV2QGFycm93LmFwYWNoZS5vcmc%3D)). > We used to postfix > these assets with the particular architecture, but we need a more robust > solution without renaming > anything (either by creating tarballs or uploading to multiple release tags). > > All-in-all it's in quite good shape, I'll work on to refactor the artifact > uploading and finish the > remaining jira tasks. IMHO we should start to test the whole release > procedure from next Monday > and ship a couple of test releases before We reach July 20th. > > - Krisztian