Some more details about Apache Airflow:
1) we announce the intention of making the release in the community and ask
people to raise any important issues they would like to get "in" (currently
we are in active development for Airflow 2.0 but we are cherry-picking
quite a number of changes to 1.10 l
Of course everyone’s welcome to participate. Best way to start is to introduce
yourself over at d...@geode.apache.org and ask your questions there.
Anthony
> On Mar 12, 2020, at 12:51 PM, Claude Edney
> wrote:
>
> Hey Anthony, Can we as engineers take alook at it before it releases? Are
Hey Anthony, Can we as engineers take alook at it before it releases? Are
there any links to view you can send me, or source code files we can see?Thanks
On Thursday, March 12, 2020, 12:55:51 PM EDT, Anthony Baker
wrote:
Geode nominally follows a quarterly release cycle, in conjunction
Geode nominally follows a quarterly release cycle, in conjunction with “don’t
release until it’s ready”. Based on past experience we allow a period of
stabilization time to shake out issues on the release branch before we create
release candidates for voting.
Anthony
> On Mar 12, 2020, at 4:
And actually - when it comes to this discussion - we will be
supper-happy if you could help us with providing other examples and some
preliminary result of your analysis... I think that would be super helpful
if you could take part in the discussion!
J.
On Thu, Mar 12, 2020 at 12:54 PM Jarek Poti
I think so far it is "release when we are ready" schedule. This is
something that we will be discussing on improving for our Airflow 2.0
schedule most likely so maybe that will be a good time to discuss it. We
will likely do some analysis of current approach, pros and cons of
different approaches -
