Thank you Boyuan. This proposal looks good to me. I agree that it would be great to agree on this before the start of the next release. The reason is we built wheel files for the past 2 releases however we do not yet have a working process. Releases are slowed down because of that. If we can address it sooner, we can avoid the same issue for the next release.
The biggest open question here is creating a new repo for the purpose of creating the wheel files. (1) Is this a concern (2) If this is not a concern, who could help us do this, would that be infra? Ahmet On Mon, Jul 16, 2018 at 2:47 PM, Boyuan Zhang <[email protected]> wrote: > Hey all, > > After 2.4.0, we also publish python wheels as part of python artifacts. In > order to make release process easier, we need a standardized way to build > and stage python wheels as s part of release process. > > In this deign proposal[1], I debriefed how we built python wheels for > 2.4.0 & 2.5.0, and proposal an approach for further release. We have > several action items in this discussion: > 1. We need someone who has the permission to create a new repo under > apache, example <https://github.com/robertwb/apache-beam-wheels>. > 2. We need to decide whether we want to create a special account with beam > commiter > permissions for release process. > 3. We need to choose a more suitable way to store credentials in travis. > > If we could make these decision asap, then it's possible for 2.6.0 release > to build python wheels using this new approach, which may save a lot of > time for release process. > > Thanks for all your attention and help! Looking forward to get feedback > from you. > > Boyuan > > [1] https://docs.google.com/document/d/1MRVFs48e6g7wORshr2UpuOVD_ > yTSJTbmR65_j8XbGek/edit?usp=sharing >
