git status

[Luke Inman-Semerau]

So, for those not paying attention on IRC. This exists:

https://github.com/krosenvold/selenium-git-release-candidate

The only thing I currently notice is the last commit on the repo was done by Kristian but that commit is not currently in svn (and that svn has had a few more commits since this was created).

So, I guess the question is, what's the plan? (Prods Simon)

My 2¢ -

since "trunk" is this 'master' branch in the seemingly proposed git repo. The websites should be branches themselves (initialized cleanly with their own history of course). I can take care of this when the time comes, I've already created git repo's for them (with full history):

https://github.com/SeleniumHQ/www.seleniumhq.org

https://github.com/lukeis/addons.seleniumhq.org

https://github.com/lukeis/selenium-grid.seleniumhq.org

Also, I'm not sure how google code handles the wiki pages, but I've created a repo with all the history for that too:

https://github.com/lukeis/selenium-wiki

A couple of other things come to mind with the potential conversion to git:

The use of svn revision in our release, should that just change to git commit revision? (I'm gonna guess yes, but it will obviously look different and hopefully no on is depending on it being an int vs. a string?)

wire.py -> JsonWireProtocol.wiki  the instructions just need to get ironed out with the new repo / potential branching.

*Big Side note to all those listening* even though I list repos in github, I know there is no intention of moving the Selenium project to github. It will remain on google code as the primary repo location where everything is built / distributed from. (Now, because git is a DVCS... I can do things like have a clone in github that I keep in sync with the main repo... and even potentially accept pull requests from as long as they requestor has signed the CLA.)

[Kristian Rosenvold]

2013/1/13 Luke Inman-Semerau <luke.s...@gmail.com>:

> So, for those not paying attention on IRC. This exists:
> https://github.com/krosenvold/selenium-git-release-candidate
>
> The only thing I currently notice is the last commit on the repo was done by
> Kristian but that commit is not currently in svn (and that svn has had a few
> more commits since this was created).

I am keeping track of the diff here, and as long as the QA process for
the release candidate does not take too long I will retro-fit the SVN
commits when we flip.

The one commit I did on the rc was to strip windows CR's from the repo.

>
> So, I guess the question is, what's the plan? (Prods Simon)
>
>
> My 2¢ -
> since "trunk" is this 'master' branch in the seemingly proposed git repo.

It will be called "master" "soon".

> The websites should be branches themselves (initialized cleanly with their
> own history of course). I can take care of this when the time comes, I've
> already created git repo's for them (with full history):
> https://github.com/SeleniumHQ/www.seleniumhq.org
> https://github.com/lukeis/addons.seleniumhq.org
> https://github.com/lukeis/selenium-grid.seleniumhq.org

Excellent !

"Someone" needs to find out how we should deal with the sites. If they
need to be on a branch in the main repo "someone else" (me) can fix
that.

>
> Also, I'm not sure how google code handles the wiki pages, but I've created
> a repo with all the history for that too:
> https://github.com/lukeis/selenium-wiki
>
>
> A couple of other things come to mind with the potential conversion to git:
> The use of svn revision in our release, should that just change to git
> commit revision? (I'm gonna guess yes, but it will obviously look different
> and hopefully no on is depending on it being an int vs. a string?)
> wire.py -> JsonWireProtocol.wiki the instructions just need to get ironed
> out with the new repo / potential branching.

r14087 = > 4c47f19af9918fabc42cfdb7ea62323a7f8279b9 once we switch.

>
>
> *Big Side note to all those listening* even though I list repos in github, I
> know there is no intention of moving the Selenium project to github. It will
> remain on google code as the primary repo location where everything is built
> / distributed from. (Now, because git is a DVCS... I can do things like have
> a clone in github that I keep in sync with the main repo... and even
> potentially accept pull requests from as long as they requestor has signed
> the CLA.)

The CLA is the key. The location of the authorative master is not that
important. In the maven repos that have been switched to git (with
master @ ASF) we have huge activity coming from gtihub.

Kristian

[Daniel Wagner-Hall]

On 13 January 2013 05:00, Luke Inman-Semerau <luke.s...@gmail.com> wrote:

So, for those not paying attention on IRC. This exists:

https://github.com/krosenvold/selenium-git-release-candidate

The only thing I currently notice is the last commit on the repo was done by Kristian but that commit is not currently in svn (and that svn has had a few more commits since this was created).

So, I guess the question is, what's the plan? (Prods Simon)

My 2¢ -

since "trunk" is this 'master' branch in the seemingly proposed git repo. The websites should be branches themselves (initialized cleanly with their own history of course). I can take care of this when the time comes, I've already created git repo's for them (with full history):

https://github.com/SeleniumHQ/www.seleniumhq.org

https://github.com/lukeis/addons.seleniumhq.org

https://github.com/lukeis/selenium-grid.seleniumhq.org

Also, I'm not sure how google code handles the wiki pages, but I've created a repo with all the history for that too:

https://github.com/lukeis/selenium-wiki

The wiki should be a separate repo (a la https://code.google.com/p/crazy-fun/source/list?repo=wiki)

 

A couple of other things come to mind with the potential conversion to git:

The use of svn revision in our release, should that just change to git commit revision? (I'm gonna guess yes, but it will obviously look different and hopefully no on is depending on it being an int vs. a string?)

wire.py -> JsonWireProtocol.wiki  the instructions just need to get ironed out with the new repo / potential branching.

*Big Side note to all those listening* even though I list repos in github, I know there is no intention of moving the Selenium project to github. It will remain on google code as the primary repo location where everything is built / distributed from. (Now, because git is a DVCS... I can do things like have a clone in github that I keep in sync with the main repo... and even potentially accept pull requests from as long as they requestor has signed the CLA.)

Thanks, guys, you are awesome! Let me know when there's something we need to have the Google Code team do.

[Simon Stewart]

Inline.

On Sun, Jan 13, 2013 at 5:00 AM, Luke Inman-Semerau <luke.s...@gmail.com> wrote:

So, for those not paying attention on IRC. This exists:

https://github.com/krosenvold/selenium-git-release-candidate

The only thing I currently notice is the last commit on the repo was done by Kristian but that commit is not currently in svn (and that svn has had a few more commits since this was created).

So, I guess the question is, what's the plan? (Prods Simon)

Kristian and I have been chatting about this on IRC. The plan is: let's do this thing.

 

My 2¢ -

since "trunk" is this 'master' branch in the seemingly proposed git repo. The websites should be branches themselves (initialized cleanly with their own history of course).

We can set them up as sub repos in Google Code. It's easy to add them.

 

I can take care of this when the time comes, I've already created git repo's for them (with full history):

https://github.com/SeleniumHQ/www.seleniumhq.org

https://github.com/lukeis/addons.seleniumhq.org

https://github.com/lukeis/selenium-grid.seleniumhq.org

Also, I'm not sure how google code handles the wiki pages, but I've created a repo with all the history for that too:

https://github.com/lukeis/selenium-wiki

Ditto the wiki

 

A couple of other things come to mind with the potential conversion to git:

The use of svn revision in our release, should that just change to git commit revision? (I'm gonna guess yes, but it will obviously look different and hopefully no on is depending on it being an int vs. a string?)

Yes, we should use the git revision. I'll hack this in once the checkouts are done.

 

wire.py -> JsonWireProtocol.wiki  the instructions just need to get ironed out with the new repo / potential branching.

Agreed.

 

*Big Side note to all those listening* even though I list repos in github, I know there is no intention of moving the Selenium project to github. It will remain on google code as the primary repo location where everything is built / distributed from. (Now, because git is a DVCS... I can do things like have a clone in github that I keep in sync with the main repo... and even potentially accept pull requests from as long as they requestor has signed the CLA.)

I'll be watching the commits to GC like a hawk. I've an intense distrust of git pushes from remote repos and the only thing that'll make me feel comfortable is vigilance.Yes, I know that makes me a paranoid curmudgeon. I'm ok with that.

Simon