[VOTE][LAZY] Migrate Commons Pool to Git

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[VOTE][LAZY] Migrate Commons Pool to Git

Matt Sicker
This is a vote by lazy consensus to migrate the commons-pool subversion
repository into git. We have been slowly migrating projects in Commons to
git, and I'd like to migrate Pool to make it easier to perform a new
release and in general because git's easier to use nowadays thanks to its
widespread use.

Any projects that may rely on using an svn external repo on this should be
able to use GitHub's svn mirroring capability, though I'm not exactly sure
if there are ASF rules against doing that in Apache projects.

This vote will be open for 72 hours. If there are no objections by then, I
will submit a request to INFRA to migrate the repo. After that, I'll update
pom.xml with the new source repository location. It could be helpful to
update the site as it's currently committed, though a new release would
contain that information as well.

--
Matt Sicker <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE][LAZY] Migrate Commons Pool to Git

garydgregory
+1

Gary


On Mar 5, 2017 6:22 PM, "Matt Sicker" <[hidden email]> wrote:

This is a vote by lazy consensus to migrate the commons-pool subversion
repository into git. We have been slowly migrating projects in Commons to
git, and I'd like to migrate Pool to make it easier to perform a new
release and in general because git's easier to use nowadays thanks to its
widespread use.

Any projects that may rely on using an svn external repo on this should be
able to use GitHub's svn mirroring capability, though I'm not exactly sure
if there are ASF rules against doing that in Apache projects.

This vote will be open for 72 hours. If there are no objections by then, I
will submit a request to INFRA to migrate the repo. After that, I'll update
pom.xml with the new source repository location. It could be helpful to
update the site as it's currently committed, though a new release would
contain that information as well.

--
Matt Sicker <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE][LAZY] Migrate Commons Pool to Git

Matt Sicker
Forgot to mention +1 from me of course.

On 5 March 2017 at 11:51, Gary Gregory <[hidden email]> wrote:

> +1
>
> Gary
>
>
> On Mar 5, 2017 6:22 PM, "Matt Sicker" <[hidden email]> wrote:
>
> This is a vote by lazy consensus to migrate the commons-pool subversion
> repository into git. We have been slowly migrating projects in Commons to
> git, and I'd like to migrate Pool to make it easier to perform a new
> release and in general because git's easier to use nowadays thanks to its
> widespread use.
>
> Any projects that may rely on using an svn external repo on this should be
> able to use GitHub's svn mirroring capability, though I'm not exactly sure
> if there are ASF rules against doing that in Apache projects.
>
> This vote will be open for 72 hours. If there are no objections by then, I
> will submit a request to INFRA to migrate the repo. After that, I'll update
> pom.xml with the new source repository location. It could be helpful to
> update the site as it's currently committed, though a new release would
> contain that information as well.
>
> --
> Matt Sicker <[hidden email]>
>



--
Matt Sicker <[hidden email]>