cutting over to Apache git repo

[James Taylor <ja...@apache.org>]

I received the last piece of paperwork I needed for us to move the code
over to Apache. The one thing we don't have is our Github issues transfered
over yet, but I don't think we have to wait for that - our JIRA is active,
we just don't have our existing issues transfered over yet.

Do you have outstanding work you'd like to get in before we switch over to
Apache? Once we switch over, everything will be re-packaged and re-licensed
and we'll basically have a new repo with just the latest source. I plan to
put the code from 2.2.2 there first, then create a branch for it, and then
replace it with the code from master. Our first release will match our
2.2.2 release (just repackaged and relicensed). Then our second release
will be based on the current master branch, planned for sometime in Feb.

Sound reasonable? How about if we target doing the cutover on Wednesday?

Thanks,
James

Re: cutting over to Apache git repo

[James Taylor <ja...@apache.org>]

FYI, current plan is to do the repository cutover tomorrow. Thanks,

James


On Tue, Jan 21, 2014 at 10:48 AM, Andrew Purtell <ap...@apache.org>wrote:

> On Mon, Jan 20, 2014 at 10:07 PM, James Taylor <jamestaylor@apache.org
> >wrote:
>
> > I plan to
> > put the code from 2.2.2 there first, then create a branch for it, and
> then
> > replace it with the code from master. Our first release will match our
> > 2.2.2 release (just repackaged and relicensed). Then our second release
> > will be based on the current master branch, planned for sometime in Feb.
> >
> > Sound reasonable? How about if we target doing the cutover on Wednesday?
> >
>
> I filed PHOENIX-8 related to this to maybe increase the activity on your
> JIRA :-)
>
>
>
> --
> Best regards,
>
>    - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>

Re: cutting over to Apache git repo

[Andrew Purtell <ap...@apache.org>]

On Mon, Jan 20, 2014 at 10:07 PM, James Taylor <ja...@apache.org>wrote:

> I plan to
> put the code from 2.2.2 there first, then create a branch for it, and then
> replace it with the code from master. Our first release will match our
> 2.2.2 release (just repackaged and relicensed). Then our second release
> will be based on the current master branch, planned for sometime in Feb.
>
> Sound reasonable? How about if we target doing the cutover on Wednesday?
>

I filed PHOENIX-8 related to this to maybe increase the activity on your
JIRA :-)



-- 
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)