You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by Markus Weimer <we...@apache.org> on 2014/10/08 20:18:33 UTC
Merging repositories and moving code into the Apache infrastructure
Hi,
were getting all the ducks in line in terms of the internal approvals to
move Microsoft Code over to the ASF. Hence, now is the time to figure out
how to do it, technically. I propose the following plan to that end:
1. We drain the Pull request queue and delete all branches we no longer
work on.
2. The GitHub repositories for Wake, Tang and REEF turn read-only
3. A git magician merges all three into one repository, preserving at
least the history of the master branch of each.
4. That merge will be imported into the Apache repository and work
resumes
After we did this, we can move on with beautifications like making all
three projects share a common master pom to clean up our builds, integrate
with the ASF build servers and so on.
We need a volunteer for step three. *whistlesAndPointsAtSergiy* :-)
Crucially, we need to agree on a timeline for this to happen. We have some
internal uses of REEF that make it inconvenient to do this before Oct 17th.
How about we aim for the week of Oct 20th for this to go down?
Any veto on that timing? Other things I missed?
Markus
Re: Merging repositories and moving code into the Apache infrastructure
Posted by Yingda Chen <yd...@gmail.com>.
Are we talking about master branches in each repository only? Or all
branches? I am OK for making master branches read-only on GitHub, but
Ideally we would like to keep those internal release branches there for a
while for bug fixing.
-Yingda
On Wed, Oct 8, 2014 at 11:18 AM, Markus Weimer <we...@apache.org> wrote:
> Hi,
>
> were getting all the ducks in line in terms of the internal approvals to
> move Microsoft Code over to the ASF. Hence, now is the time to figure out
> how to do it, technically. I propose the following plan to that end:
>
>
> 1. We drain the Pull request queue and delete all branches we no longer
> work on.
> 2. The GitHub repositories for Wake, Tang and REEF turn read-only
> 3. A git magician merges all three into one repository, preserving at
> least the history of the master branch of each.
> 4. That merge will be imported into the Apache repository and work
> resumes
>
> After we did this, we can move on with beautifications like making all
> three projects share a common master pom to clean up our builds, integrate
> with the ASF build servers and so on.
>
> We need a volunteer for step three. *whistlesAndPointsAtSergiy* :-)
>
> Crucially, we need to agree on a timeline for this to happen. We have some
> internal uses of REEF that make it inconvenient to do this before Oct 17th.
> How about we aim for the week of Oct 20th for this to go down?
>
> Any veto on that timing? Other things I missed?
>
> Markus
>
Re: Merging repositories and moving code into the Apache infrastructure
Posted by Byung-Gon Chun <bg...@gmail.com>.
Hi,
The week of Oct 20th works pretty well for SNU.
Thanks.
-Gon
On Wed, Oct 8, 2014 at 12:18 PM, Markus Weimer <we...@apache.org> wrote:
> Hi,
>
> were getting all the ducks in line in terms of the internal approvals to
> move Microsoft Code over to the ASF. Hence, now is the time to figure out
> how to do it, technically. I propose the following plan to that end:
>
>
> 1. We drain the Pull request queue and delete all branches we no longer
> work on.
> 2. The GitHub repositories for Wake, Tang and REEF turn read-only
> 3. A git magician merges all three into one repository, preserving at
> least the history of the master branch of each.
> 4. That merge will be imported into the Apache repository and work
> resumes
>
> After we did this, we can move on with beautifications like making all
> three projects share a common master pom to clean up our builds, integrate
> with the ASF build servers and so on.
>
> We need a volunteer for step three. *whistlesAndPointsAtSergiy* :-)
>
> Crucially, we need to agree on a timeline for this to happen. We have some
> internal uses of REEF that make it inconvenient to do this before Oct 17th.
> How about we aim for the week of Oct 20th for this to go down?
>
> Any veto on that timing? Other things I missed?
>
> Markus
>
--
Byung-Gon Chun
Re: Merging repositories and moving code into the Apache
infrastructure
Posted by "Mattmann, Chris A (3980)" <ch...@jpl.nasa.gov>.
Sounds gr8! Nice plan Markus..
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519, Mailstop: 168-527
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Associate Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-----Original Message-----
From: Markus Weimer <we...@apache.org>
Reply-To: "dev@reef.incubator.apache.org" <de...@reef.incubator.apache.org>
Date: Wednesday, October 8, 2014 at 11:18 AM
To: "dev@reef.incubator.apache.org" <de...@reef.incubator.apache.org>
Subject: Merging repositories and moving code into the Apache
infrastructure
>Hi,
>
>were getting all the ducks in line in terms of the internal approvals to
>move Microsoft Code over to the ASF. Hence, now is the time to figure out
>how to do it, technically. I propose the following plan to that end:
>
>
> 1. We drain the Pull request queue and delete all branches we no longer
> work on.
> 2. The GitHub repositories for Wake, Tang and REEF turn read-only
> 3. A git magician merges all three into one repository, preserving at
> least the history of the master branch of each.
> 4. That merge will be imported into the Apache repository and work
> resumes
>
>After we did this, we can move on with beautifications like making all
>three projects share a common master pom to clean up our builds, integrate
>with the ASF build servers and so on.
>
>We need a volunteer for step three. *whistlesAndPointsAtSergiy* :-)
>
>Crucially, we need to agree on a timeline for this to happen. We have some
>internal uses of REEF that make it inconvenient to do this before Oct
>17th.
>How about we aim for the week of Oct 20th for this to go down?
>
>Any veto on that timing? Other things I missed?
>
>Markus