Hi,

In LEGAL-339 <https://issues.apache.org/jira/browse/LEGAL-339> it was
concluded that we can in fact move the code to Apache git and cut Apache
releases without the SGA. I propose we move forward on that. I suggest the
following plan:

1.a Refactor all Heron build dependencies (mainly c++ libs) to be fetched
at build time and not committed in the repo. (#2092
<https://github.com/twitter/heron/issues/2092>)
1.b Refactor the bazel checkstyles to support both the Twitter copyright
(for existing code) and the Apache copyright (for new code after the
migration).
2. Cut the last non-Apache release.
3. Migrate the code to Apache git
4. Add incubation disclaimer
5. Cut the first Apache release.

What do folks think of that plan? Item's 1a and 1b can happen in parallel,
as could item 2 actually. There will surely be more smaller items, but
those are the big ones as I see it. Please chime in if I've overlooked
anything major.

thanks,
Bill

Reply via email to