Hi, I have a sandbox cluster at work (3 EC2 VMs + Celery on Elasticache) that I have been running 1.10 on. This is because we want to test in advance the Kubernetes operator and RBAC. Happy to lend some assistance with that.
-James M. On Fri, Jun 15, 2018 at 6:28 AM, Driesprong, Fokko <[email protected]> wrote: > Hi all, > > As you might know, I'm a consultant at GoDataDriven and I just changed to a > different project. At this project they are not using Airflow (yet), so for > me it is hard to test the RC's etc. I'm willing to help in the process, but > currently I'm struggling to find time for the project on the side > (including Airflow). > > Cheers, Fokko > > 2018-06-13 23:28 GMT+02:00 Bolke de Bruin <[email protected]>: > > > Same here and will be for a while still :-(. So unfortunately 1.10 is a > > bit stalled. > > > > B, > > > > > On 13 Jun 2018, at 17:16, Chris Riccomini <[email protected]> > wrote: > > > > > > Hey Fokko, > > > > > > Sorry that I've been MIA for a while. Just wanted to check in on 1.10, > > and > > > its current status. > > > > > > Cheers, > > > Chris > > > > > > On Tue, May 1, 2018 at 11:18 PM Driesprong, Fokko <[email protected] > > > > > wrote: > > > > > >> Hi Bryon, > > >> > > >> We'll be releasing the RC's soon. If there aren't much issues with the > > >> RC's, it will be released quickly. But we need the community to test > > these. > > >> > > >> Cheers, Fokko > > >> > > >> 2018-05-01 20:57 GMT+02:00 Wicklund, Bryon <[email protected] > >: > > >> > > >>> Hey I was wondering if you had a date in mind or an estimate for when > > >>> Airflow 1.10.0 will be released? > > >>> > > >>> Thanks! > > >>> -Bryon > > >>> > > >>> This e-mail, including attachments, may include confidential and/or > > >>> proprietary information, and may be used only by the person or entity > > >>> to which it is addressed. If the reader of this e-mail is not the > > >> intended > > >>> recipient or his or her authorized agent, the reader is hereby > notified > > >>> that any dissemination, distribution or copying of this e-mail is > > >>> prohibited. If you have received this e-mail in error, please notify > > the > > >>> sender by replying to this message and delete this e-mail > immediately. > > >>> > > >> > > > > >
