I changed the title for the duration of the move
On Wed, May 4, 2016 at 12:20 PM, Maxime Beauchemin < [email protected]> wrote: > About the migration, I just released the Airflow repo to `asfgit` as > requested. > > For some reason I had to assign it to myself first, so the repo will > appear here <https://github.com/mistercrunch/airflow> until Apache Infra > accepts the repo and moves it to it's final destination. > > This should not affect any normal flows, perhaps just a bit of confusion > if you pay attention to URLs. > > Follow the progress here: > https://issues.apache.org/jira/browse/INFRA-11776 > > If anyone knows of a way to accelerate this please do! > > On Wed, May 4, 2016 at 12:04 PM, Maxime Beauchemin < > [email protected]> wrote: > >> Github has a branch protection feature that prevents force pushes and >> branch deletion. I just turned it on for `master`. >> >> >> >> >> On Wed, May 4, 2016 at 11:18 AM, Siddharth Anand < >> [email protected]> wrote: >> >>> Yes.. also, I'm hoping no one does a "force push" in this scenario. >>> -s >>> >>> On Wednesday, May 4, 2016 5:05 PM, Jeremiah Lowin <[email protected]> >>> wrote: >>> >>> >>> Let's make sure that process is well documented! >>> >>> (asking for a friend... who doesn't want to accidentally erase Airflow) >>> >>> On Wed, May 4, 2016 at 12:59 PM Chris Riccomini <[email protected]> >>> wrote: >>> >>> > > Chris, I assume the merge button will be greyed on PRs, what's the >>> new >>> > PR acceptance >>> > flow like? >>> > >>> > I believe we'll have to pull the PR locally, merge into master, and >>> push >>> > master to the Apache Git repo. Annoying, but should work. >>> > >>> > On Tue, May 3, 2016 at 5:58 PM, Maxime Beauchemin < >>> > [email protected]> wrote: >>> > >>> > > Hi, >>> > > >>> > > I'll be proceeding with the repo migration tomorrow as planned, >>> getting >>> > > things started in the morning. From previous experiences migrating >>> repos >>> > on >>> > > Github, the transition should be smooth where Github handles all of >>> the >>> > > redirection. Even Travis and other Github ecosystem tools should just >>> > work. >>> > > >>> > > Chris, I assume the merge button will be greyed on PRs, what's the >>> new PR >>> > > acceptance flow like? >>> > > >>> > > Thanks, >>> > > >>> > > Max >>> > > >>> > > On Tue, May 3, 2016 at 4:28 PM, Siddharth Anand <[email protected]> >>> > wrote: >>> > > >>> > > > Committers/Maintainers : >>> > > > If you have an open item on >>> > > > >>> > >>> https://cwiki.apache.org/confluence/display/AIRFLOW/Migrating+to+Apache, >>> > > > please send status/blockers on your items : >>> > > > Specifically: >>> > > > - Max (repo migration) >>> > > > - Jeremiah (travis migration) >>> > > > >>> > > > - I know you are waiting on Max >>> > > > >>> > > > - Bolke >>> > > > >>> > > > - GH issue-to-Jira migration - it looks like we decided to >>> handle >>> > this >>> > > > in a lazy fashion, so maybe we can close this? >>> > > > -s >>> > > >>> > >>> >>> >>> >>> >> >> >
