Alright -- sounds like we have a consensus to proceed with the first stable release after 0.6.0, targeting end of March / early April. I'll kick off separate threads for specific decisions we need to make.
On Thu, Feb 23, 2017 at 6:07 AM, Aljoscha Krettek <aljos...@apache.org> wrote: > I think we're ready for this! The public APIs are in very good shape, > especially now that we have the new DoFn, user facing state and timers and > splittable DoFn. Not all Runners support the more advanced features but we > can work on this after a stable release and there are enough runners that > support a large part of the features. > > Best, > Aljoscha > > On Thu, 23 Feb 2017 at 06:15 Kenneth Knowles <k...@google.com.invalid> > wrote: > > > On Wed, Feb 22, 2017 at 5:35 PM, Chamikara Jayalath < > chamik...@apache.org> > > wrote: > > > > > > I think, this point applies to Python SDK as well (though as you > > mentioned, > > > API hiding in Python is a mere convention (prefix with underscore) not > > > enforced. We already have mechanism for marking APIs as deprecated > which > > > might be useful here: > > > https://github.com/apache/beam/blob/master/sdks/python/ > > > apache_beam/utils/annotations.py > > > > > > - Cham > > > > > > > Perhaps an explicit @public annotation would fit. I could imagine easily > > generating a spec to check against from such annotations, though tooling > is > > secondary to documentation. > > > > Kenn > > >
