Hey Bolke/Max, Thanks for taking this on! :) The first time release-tax is expensive.
> In addition I do have some question about the release process in general as > there seems to be a gap between the vote and how (specifically by whom) it > gets published to the podling release pages. Are you referring to this? http://incubator.apache.org/projects/airflow.html Cheers, Chris On Fri, Sep 2, 2016 at 9:48 AM, Maxime Beauchemin <[email protected]> wrote: > Hi, > > The changes Bolke an I made are summarized in this PR on my fork that diffs > the changes needed against the latest release: > https://github.com/mistercrunch/incubator-airflow/pull/1 > > I wasn't able to run the the license check at `scripts/ci/check-license.sh` > (still running after 1+ hour...) but checked the Google Cloud operators > and the ones I opened looked ok. > > About the GH authentication backend, I removed it so that we can move > forward with the release. We'll have to mention it in the release notes. I > suggest we leave it in master for now and take it off prior to the next > official release if no one from the community steps up to fix the issue. > > Thanks, > > Max > > On Fri, Sep 2, 2016 at 4:52 AM, Bolke de Bruin <[email protected]> wrote: > >> Hi All, >> >> Max and I did some work to prepare the Apache release. We are close to >> have it available for voting, just some small bits need to be done. In >> addition I do have some question about the release process in general as >> there seems to be a gap between the vote and how (specifically by whom) it >> gets published to the podling release pages. @Jakob @Chris can you guys >> clarify this? >> >> I have made my signing keys available at the key servers and published >> them at http://people.apache.org/~bolke/ . We are planning to make the >> ‘pre-vote' release available for verification also at this location. >> >> Updates that we (Max mostly) have done in addition to previous compliancy >> efforts: >> >> * Removed notices to highcharts >> * Add DISCLAIMER file >> * Removed copyright notices >> * Some updates on how we version >> >> To be done: >> * Add license headers to Google Cloud Operators (we won’t introduce the >> new ones) >> * Deal with the security issue in the GitHub authentication backend. >> >> That last issue raises some problems for us as we both are not using this >> integration and cannot test it. Still it feels a bit wrong to release with >> a security issue. Is someone able to pick this up in the coming days? >> >> Cheers >> Bolke
