I'm find with the next release being 2.0 instead of 1.10, provided that we have a very explicit list of what is going into 2.0, and that we make sure that the list is not too long, so we can get 2.0 out. Let me start a separate thread.
On Wed, Dec 13, 2017 at 3:04 PM, Maxime Beauchemin < maximebeauche...@gmail.com> wrote: > Yes, and deprecate the things that have been logging.warn for a while. > > Max > > On Wed, Dec 13, 2017 at 1:19 PM, Bolke de Bruin <bdbr...@gmail.com> wrote: > > > Can we make that 2.0? Ie. skip 1.10? With the many changes that are > > scheduled: new web ui, time zone support I think it would make sense. > Maybe > > we should move some api stuff out of experimental as well. > > > > B. > > > > Verstuurd vanaf mijn iPad > > > > > Op 13 dec. 2017 om 20:14 heeft Chris Riccomini <criccom...@apache.org> > > het volgende geschreven: > > > > > > Hey Vincent, > > > > > >> When you say "we're going to be moving over to it", do you mean that > > it's > > > in the official roadmap? > > > > > > Yes. We first discussed RBAC back in August: > > > > > > https://lists.apache.org/thread.html/31bbf40f256bc469e578aa4098d631 > > e9aa3e644bf555309e3729bcfc@%3Cdev.airflow.apache.org%3E > > > > > > We then had a meeting to discuss the work, which was advertised in the > > dev@ > > > mailing list. > > > > > > Since then, Joy Gao has been working on updating the webserver: > > > > > > https://lists.apache.org/thread.html/a95c0c307d68d2a5196705987b3d80 > > 788882e74b4106908da8bff83c@%3Cdev.airflow.apache.org%3E > > > > > > And has presented on the topic at the last SF bay area Airflow meetup. > > > > > > The plan is to merge this webserver into master before 1.10 is released > > > (i.e. in the next month or two). From there we would eventually > deprecate > > > and remove the legacy UI. > > > > > > Cheers, > > > Chris > > > > > > On Wed, Dec 13, 2017 at 10:19 AM, Rafael Gomes <cont...@rafagomes.com> > > > wrote: > > > > > >> If we have an official roadmap I would like to help. > > >> > > >> On Dec 13, 2017 1:13 PM, "vincent.fh.lo...@gmail.com" < > > >> vincent.fh.lo...@gmail.com> wrote: > > >> > > >>> Hi Chris, > > >>> > > >>> Thanks for the link, really nice. > > >>> When you say "we're going to be moving over to it", do you mean that > > it's > > >>> in the official roadmap? > > >>> > > >>> Thanks, > > >>> Vincent > > >>> > > >>>> On 2017-12-12 17:53, Chris Riccomini <criccom...@apache.org> wrote: > > >>>> (Note, FAB = https://github.com/dpgaspar/Flask-AppBuilder) > > >>>> > > >>>> > > >>>> > > >>>> On Tue, Dec 12, 2017 at 8:52 AM, Chris Riccomini < > > >> criccom...@apache.org> > > >>>> wrote: > > >>>> > > >>>>> If you are looking at implementing this, I'd suggest looking at FAB > > >> and > > >>>>> https://github.com/wepay/airflow-webserver. FAB has a much cleaner > > >>>>> security model than the current UI, and we're going to be moving > over > > >>> to > > >>>>> it. If FAB doesn't support SAML 2.0 (I don't think it does), I > think > > >>>>> patching it to do so would be a way to get what you want. > > >>>>> > > >>>>> On Tue, Dec 12, 2017 at 6:35 AM, Gerard Toonstra < > > >> gtoons...@gmail.com> > > >>>>> wrote: > > >>>>> > > >>>>>> Hello, > > >>>>>> > > >>>>>> Has anyone looked at / implemented /disconsidered saml2.0 > > >>> authentication > > >>>>>> for airflow? Did a search on google, but this didn't return > > >> anything > > >>>>>> specific. > > >>>>>> > > >>>>>> Rgds, > > >>>>>> > > >>>>>> Gerard > > >>>>>> > > >>>>> > > >>>>> > > >>>> > > >>> > > >> > > >
