svn+git

[Alan Harder-2]

Kohsuke/all-

Looks like opt-in migration of plugins over to github is working fine, as seen by requests here to update ci.hudson-labs.org jobs over to github.. I'm recommending that plugin maintainers remove the code in java.net svn when they make the move to github.. I'll repeat that here:

NOTE: All plugin maintainers switching their build jobs over to github, please remove the code in java.net svn and replace with a README.TXT as done here for jira plugin:
http://java.net/projects/hudson/sources/svn/revision/37608
http://java.net/projects/hudson/sources/svn/show/trunk/hudson/plugins/jira

However, I'm still concerned that github has master branches for plugins that have not made github their official repo.  I have seen commits of localization changes in github for my plugins, but I have not switched over to github.  In the same way that plugins moving to github should replace code in svn with a README, I think github should have only the "svn" branch for plugins that have NOT moved to github, no master branch, to avoid commits in the wrong place.
Do you agree? and who can make this change?
Thanks,

    - Alan 

On vacation:
I will be out of the office starting the Dec. 23rd and
will return on January 10.

for any problem related to your email or computer, please send an email to [hidden email].

For any emergency, call at 1-418-264-6911

[Andrew Bayer]

I agree - Kohsuke's busy this week with family stuff, but I think he's probably the right person to handle that, since he's got the scripts that are keeping everything in sync.

A.

On Fri, Dec 24, 2010 at 4:09 AM, Alan Harder <[hidden email]> wrote:

Kohsuke/all-

Looks like opt-in migration of plugins over to github is working fine, as seen by requests here to update ci.hudson-labs.org jobs over to github.. I'm recommending that plugin maintainers remove the code in java.net svn when they make the move to github.. I'll repeat that here:

NOTE: All plugin maintainers switching their build jobs over to github, please remove the code in java.net svn and replace with a README.TXT as done here for jira plugin:
http://java.net/projects/hudson/sources/svn/revision/37608
http://java.net/projects/hudson/sources/svn/show/trunk/hudson/plugins/jira

However, I'm still concerned that github has master branches for plugins that have not made github their official repo.  I have seen commits of localization changes in github for my plugins, but I have not switched over to github.  In the same way that plugins moving to github should replace code in svn with a README, I think github should have only the "svn" branch for plugins that have NOT moved to github, no master branch, to avoid commits in the wrong place.
Do you agree? and who can make this change?
Thanks,

    - Alan 

On vacation:
I will be out of the office starting the Dec. 23rd and
will return on January 10.

for any problem related to your email or computer, please send an email to [hidden email].

For any emergency, call at 1-418-264-6911

[Alan Harder-2]

bump..

On 12/24/10 5:48 AM, Andrew Bayer wrote:

I agree - Kohsuke's busy this week with family stuff, but I think he's probably the right person to handle that, since he's got the scripts that are keeping everything in sync.

A.

On Fri, Dec 24, 2010 at 4:09 AM, Alan Harder <[hidden email]> wrote:

Kohsuke/all-

Looks like opt-in migration of plugins over to github is working fine, as seen by requests here to update ci.hudson-labs.org jobs over to github.. I'm recommending that plugin maintainers remove the code in java.net svn when they make the move to github.. I'll repeat that here:

NOTE: All plugin maintainers switching their build jobs over to github, please remove the code in java.net svn and replace with a README.TXT as done here for jira plugin:
http://java.net/projects/hudson/sources/svn/revision/37608
http://java.net/projects/hudson/sources/svn/show/trunk/hudson/plugins/jira

However, I'm still concerned that github has master branches for plugins that have not made github their official repo.  I have seen commits of localization changes in github for my plugins, but I have not switched over to github.  In the same way that plugins moving to github should replace code in svn with a README, I think github should have only the "svn" branch for plugins that have NOT moved to github, no master branch, to avoid commits in the wrong place.
Do you agree? and who can make this change?
Thanks,

    - Alan 

On vacation:
I will be out of the office starting the Dec. 23rd and
will return on January 10.

for any problem related to your email or computer, please send an email to [hidden email].

For any emergency, call at 1-418-264-6911

[Kohsuke Kawaguchi-4]

On 12/23/2010 08:09 PM, Alan Harder wrote:

>
>
> Kohsuke/all-
>
> Looks like opt-in migration of plugins over to github
> is working fine, as seen by requests here to update ci.hudson-labs.org
> jobs over to github.. I'm recommending that plugin maintainers remove
> the code in java.net svn when they make the move to github.. I'll repeat
> that here:
>
> NOTE: All plugin maintainers switching their build jobs
> over to github, please remove the code in java.net svn and replace with
> a README.TXT as done here for jira
> plugin:
> http://java.net/projects/hudson/sources/svn/revision/37608
> http://java.net/projects/hudson/sources/svn/show/trunk/hudson/plugins/jira

+1


> However, I'm still concerned that github has master branches for
> plugins that have not made github their official repo. I have seen
> commits of localization changes in github for my plugins, but I have not
> switched over to github. In the same way that plugins moving to github
> should replace code in svn with a README, I think github should have
> only the "svn" branch for plugins that have NOT moved to github, no
> master branch, to avoid commits in the wrong place.
> Do you agree? and
> who can make this change?

Getting rid of the master branch doesn't really avoid the confusion.

Maybe I can bulk-set the repository description to indicate that the
master copy is still in Subversion? And let people update them back when
they move?

--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/

On vacation:
I will be out of the office starting the Dec. 23rd and
will return on January 10.

for any problem related to your email or computer, please send an email to [hidden email].

For any emergency, call at 1-418-264-6911

[Alan Harder-2]

On 1/3/11 3:42 PM, Kohsuke Kawaguchi wrote:

>> plugins that have not made github their official repo. I have seen
>> commits of localization changes in github for my plugins, but I have not
>> switched over to github. In the same way that plugins moving to github
>> should replace code in svn with a README, I think github should have
>> only the "svn" branch for plugins that have NOT moved to github, no
>> master branch, to avoid commits in the wrong place.
>> Do you agree? and
>> who can make this change?
> However, I'm still concerned that github has master branches for
>
> Getting rid of the master branch doesn't really avoid the confusion.
>
> Maybe I can bulk-set the repository description to indicate that the
> master copy is still in Subversion? And let people update them back when
> they move?
>

Hm, no master branch at least removes a place to commit changes that won't
really be used (is the svn branch is read-only?).
But yes, repo description would help too.. make it big/bold!
Thanks,

     - Alan

On vacation:
I will be out of the office starting the Dec. 23rd and
will return on January 10.

for any problem related to your email or computer, please send an email to [hidden email].

For any emergency, call at 1-418-264-6911