New repository is not a ticket, it is a self-serve thing. That said, you probably want to develop the proposal a bit further, understanding/educating others about the benefits of what you are proposing, any alternatives, why a repository is needed, why the sample repository has Travis CI when everything else is on Jenkins, how this fits into other decisions about repository management, and so on. Anything can be done, of course, but I'd suggest developing (or communicating, or educating) a bit more.
(I'm fine with any approach.) On Fri, Aug 3, 2018 at 3:29 PM, Ahmet Altay <[email protected]> wrote: > This LGTM, also greatly simplifies the creation of wheel files for > multiple platforms. > > I can file an INFRA ticket to create a new repo to host wheel setup. Does > anybody have experience with setting up a new repo similar to this? > > Ahmet > > On Fri, Aug 3, 2018 at 1:16 PM, Boyuan Zhang <[email protected]> wrote: > >> Hey all, >> >> I'm Boyuan Zhang from Google Dataflow Team, currently helping Release >> Manager(Pablo Estrada) with 2.6.0 release. Since Beam decided to release >> python wheels since 2.5.0, we need to create a wrapper repository(sample >> repo <https://github.com/boyuanzz/apache-beam-wheels>) under apache to >> build and stage released python wheels for each release. Anyone can help to >> create this repository? >> >> Thanks for all your help! Happy Friday~ >> >> Boyuan Zhang >> > >
