Yeah. I'd probably leave it to the first 2.0.0 release. I think we have a little less stakes there and upgrading PIP is quite a bit easier (and in many cases automated). So reaching out immediately at the 2.0.0 release is probably better idea. I think we can coordinate it and knowing that release is going to happen in couple of days we can ask everyone to reach out at the MOMENT we push the release button :)
J. On Wed, Dec 9, 2020 at 3:33 PM Ash Berlin-Taylor <a...@apache.org> wrote: > Tough one. > > Yes, this is a good idea, but it does possible skirt the apache rules > about snapshots/rcs only being for "members of the dev community" or what > ever the phrasing is. > > On Wed, 9 Dec, 2020 at 15:14, Jarek Potiuk <jarek.pot...@polidea.com> > wrote: > > Hello everyone, > > One thing that I've learned from the recent PIP release is that there is > never enough reaching out when you publish a new release. > > I thought of what we can do additionally to all the social/slack/devlist > messages and talks and I think with the Airflow Summit/Meetups we have a > great way of reaching out actively. > > We could prepare a message, something like "Please test 2.0.0rc1 - we need > your help" (but a bit longer I think) and ask all the meetup organizers to > send it to their crowd, similarly with speakers from the Airflow Summit. > > Do you think this is a good idea? Is the coming RC1 today a good time for > it? Or should we wait until the actual release (per Apache Rules of > announcing release candidates ?) > > WDYT? > > J. > > > -- > > Jarek Potiuk > Polidea <https://www.polidea.com/> | Principal Software Engineer > > M: +48 660 796 129 <+48660796129> > [image: Polidea] <https://www.polidea.com/> > > -- Jarek Potiuk Polidea <https://www.polidea.com/> | Principal Software Engineer M: +48 660 796 129 <+48660796129> [image: Polidea] <https://www.polidea.com/>
