rspec users - Nov 2007 - Lighthouse and Engine Yard sponsorships

Hey all,

I''m very happy to announce that ActiveReload[1] has generously offered
to sponsor a lighthouse[2] account for rspec. We''ll be moving ticket
tracking there. We''ve already got the account set up and will soon
make it public.

We''re also going to be getting a sponsored slice at Engine Yard[3] to
host source control, which will be either mercurial or git (TBD but
we''re leaning towards mercurial). We''ll continue to push
source to svn
at rubyforge, so those of you who prefer to stay with svn can do so,
but those changes will likely be pushed once daily as opposed to every
commit.

It''s going to take some time before we get these new systems up and
operational. We''ll make additional announcements as we get closer to
actually making the moves.

Cheers,
David

[1] http://activereload.net
[2] http://lighthouseapp.com/
[3] http://engineyard.com

On Nov 18, 2007, at 4:10 PM, David Chelimsky wrote:
> Hey all,
>
> I''m very happy to announce that ActiveReload[1] has generously
offered
> to sponsor a lighthouse[2] account for rspec. We''ll be moving
ticket
> tracking there. We''ve already got the account set up and will soon
> make it public.
>
> We''re also going to be getting a sponsored slice at Engine Yard[3]
to
> host source control, which will be either mercurial or git (TBD but
> we''re leaning towards mercurial). We''ll continue to push
source to svn
> at rubyforge, so those of you who prefer to stay with svn can do so,
> but those changes will likely be pushed once daily as opposed to every
> commit.
>
> It''s going to take some time before we get these new systems up
and
> operational. We''ll make additional announcements as we get closer
to
> actually making the moves.
Out of curiosity, is there a way for subversion to check out from a  
git or mercurial repository?

Also - why are you favoring mercurial over git?

Scott

On Nov 19, 2007 8:24 AM, Scott Taylor <mailing_lists at railsnewbie.com>
wrote:
>
> On Nov 18, 2007, at 4:10 PM, David Chelimsky wrote:
>
> > Hey all,
> >
> > I''m very happy to announce that ActiveReload[1] has
generously offered
> > to sponsor a lighthouse[2] account for rspec. We''ll be moving
ticket
> > tracking there. We''ve already got the account set up and will
soon
> > make it public.
> >
> > We''re also going to be getting a sponsored slice at Engine
Yard[3] to
> > host source control, which will be either mercurial or git (TBD but
> > we''re leaning towards mercurial). We''ll continue to
push source to svn
> > at rubyforge, so those of you who prefer to stay with svn can do so,
> > but those changes will likely be pushed once daily as opposed to every
> > commit.
> >
> > It''s going to take some time before we get these new systems
up and
> > operational. We''ll make additional announcements as we get
closer to
> > actually making the moves.
>
> Out of curiosity, is there a way for subversion to check out from a
> git or mercurial repository?
>
> Also - why are you favoring mercurial over git?
>
> Scott
>
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
Please use Git.  I''ve just got to know  it ;)
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/rspec-users/attachments/20071119/81336474/attachment.html

On Nov 18, 2007 6:17 PM, Daniel N <has.sox at gmail.com> wrote:
> Please use Git.  I''ve just got to know  it ;)
>
Please use Mercurial.  I''ve just got to know it.  ;)

(Actually, I don''t much mind; I have Mercurial installed, but I
don''t have
to interact with rspec source control often enough to mind so much what you
use.  It''s far more important for the committers to pick the tool that
works
for them.)

  - Geoffrey
-- 
Geoffrey Wiseman
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/rspec-users/attachments/20071118/4e38ef9a/attachment.html

I don''t intend to use RSpec source either, but I suspect the most
people would be satisfied with a main Subversion repository. Git users
can check out from / in to a Subversion repository just fine.

On Nov 18, 2007 4:28 PM, Geoffrey Wiseman <geoffrey.wiseman at gmail.com>
wrote:
> On Nov 18, 2007 6:17 PM, Daniel N <has.sox at gmail.com> wrote:
>
> >
> >
> > Please use Git.  I''ve just got to know  it ;)
> >
>
> Please use Mercurial.  I''ve just got to know it.  ;)
>
> (Actually, I don''t much mind; I have Mercurial installed, but I
don''t have
> to interact with rspec source control often enough to mind so much what you
> use.  It''s far more important for the committers to pick the tool
that works
> for them.)
>
>   - Geoffrey
> --
> Geoffrey Wiseman
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

On Nov 18, 2007 9:57 PM, Kevin Williams <kevwil at gmail.com>
wrote:
> I don''t intend to use RSpec source either, but I suspect the most
> people would be satisfied with a main Subversion repository. Git users
> can check out from / in to a Subversion repository just fine.
>
That poses a problem for the poor souls trapped in Windows.

Yeah, there is mingw-git, but not so fancy and powerful like the *nix
users could enjoy.

Mercurial, like Bazaar play nice with windows, so I''ll not have a
problem with that.

Regarding use of packages vs. code is a problem when you need to
"update" your plugins (rspec and rspec_on_rails) if a bug you found
with the release got fixed in the repository.

-- 
Luis Lavena
Multimedia systems
-
Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi

On 11/18/07, Luis Lavena <luislavena at gmail.com>
wrote:
> On Nov 18, 2007 9:57 PM, Kevin Williams <kevwil at gmail.com> wrote:
> > I don''t intend to use RSpec source either, but I suspect the
most
> > people would be satisfied with a main Subversion repository. Git users
> > can check out from / in to a Subversion repository just fine.
> >
>
> That poses a problem for the poor souls trapped in Windows.
No it doesn''t. Subversion works great on Windows. Windows users can
try to use Git in Cygwin if they really want to, but they can also
just use TortoiseSVN or whatever favorite Subversion client they want.

With a Subversion repository, you can choose between Subversion as a
client or Git as a client (yes, it''s actually a local clone of the
repository, but a client of the main svn repo as well).

http://git.or.cz/course/svn.html
http://blog.nbwd.co.uk/2007/8/16/using-git-for-rails-development

Mercurial is a great system. I love the x-platform nature, and it
works great. I love the svn-like aliases such as "hg up" or "hg
ci -m
''foo''". I''ve used it on a number of projects.
I''ve since switched to
Git because I like the branching/merging behavior much better and
because you can clone from and commit back to a Subversion repository.
Choosing Mercurial is fine, but choosing a Subversion repository might
please more people in the long run. Just an idea, not my religion. :)

On Nov 19, 2007 1:21 AM, Kevin Williams <kevwil at gmail.com>
wrote:
> On 11/18/07, Luis Lavena <luislavena at gmail.com> wrote:
> > On Nov 18, 2007 9:57 PM, Kevin Williams <kevwil at gmail.com>
wrote:
> > > I don''t intend to use RSpec source either, but I suspect
the most
> > > people would be satisfied with a main Subversion repository. Git
users
> > > can check out from / in to a Subversion repository just fine.
> > >
> >
> > That poses a problem for the poor souls trapped in Windows.
>
> No it doesn''t. Subversion works great on Windows. Windows users
can
> try to use Git in Cygwin if they really want to, but they can also
> just use TortoiseSVN or whatever favorite Subversion client they want.
>
I wasn''t talking about the svn clone, was talking about the sync
policy "will be synch''ed one time at day"...

That in combination with Git, make difficult to be "out of the box"
useful.

the use of cygwin git is a bit problematic, and sometimes eol styles
mixes don''t like the different interpreters (unix eol against windows
eol) with ruby-mswin32 and ruby cygwin.
> With a Subversion repository, you can choose between Subversion as a
> client or Git as a client (yes, it''s actually a local clone of the
> repository, but a client of the main svn repo as well).
>
> http://git.or.cz/course/svn.html
> http://blog.nbwd.co.uk/2007/8/16/using-git-for-rails-development
>
Again, was talking about that the git-to-svn sync.
> Mercurial is a great system. I love the x-platform nature, and it
> works great. I love the svn-like aliases such as "hg up" or
"hg ci -m
> ''foo''". I''ve used it on a number of
projects. I''ve since switched to
> Git because I like the branching/merging behavior much better and
> because you can clone from and commit back to a Subversion repository.
> Choosing Mercurial is fine, but choosing a Subversion repository might
> please more people in the long run. Just an idea, not my religion. :)
Bazaar also allow you repositories that share revision information
between branches. I use it to patch upstream projects until they
commit the fixes I sent to them :-)

The git/mercurial over svn without a proper sync solution will be a
problem for those users using script/plugin to install and use rspec
on Rails applications -- since rails is highly integrated with svn for
these commands.

Anyway, just my comments :-)

-- 
Luis Lavena
Multimedia systems
-
Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi

Luis Lavena wrote:
> the use of cygwin git is a bit problematic, and sometimes eol styles
> mixes don''t like the different interpreters (unix eol against
windows
> eol) with ruby-mswin32 and ruby cygwin.
Yeah, I''ll echo this. I do a lot of work with Perl, and it''s a
real bear
to port Cygwin Perl scripts to ActiveState Perl because of this 
end-of-line nonsense. As far as I''m concerned, if you want to run Linux
on a Windows machine, buy VMWare Workstation or download the free VMWare 
Server.

On Nov 19, 2007 8:55 AM, Luis Lavena <luislavena at gmail.com>
wrote:
> On Nov 19, 2007 1:21 AM, Kevin Williams <kevwil at gmail.com> wrote:
> > On 11/18/07, Luis Lavena <luislavena at gmail.com> wrote:
> > > On Nov 18, 2007 9:57 PM, Kevin Williams <kevwil at
gmail.com> wrote:
> > > > I don''t intend to use RSpec source either, but I
suspect the most
> > > > people would be satisfied with a main Subversion repository.
Git users
> > > > can check out from / in to a Subversion repository just
fine.
> > > >
> > >
> > > That poses a problem for the poor souls trapped in Windows.
> >
> > No it doesn''t. Subversion works great on Windows. Windows
users can
> > try to use Git in Cygwin if they really want to, but they can also
> > just use TortoiseSVN or whatever favorite Subversion client they want.
> >
>
> I wasn''t talking about the svn clone, was talking about the sync
> policy "will be synch''ed one time at day"...
I was suggesting to have only one main Subversion repository rather
than two different repositories, so there would be no sync. If there
are two repositories (one Git/Mercurial at EngineYard, one Subversion
at Rubyforge) then certainly getting the sync right is important.
>
> That in combination with Git, make difficult to be "out of the
box" useful.
I''m not aware of anything special in Mercurial that would make this
easier than Git out of the box. It seems Git would be easier, with
full two-way sync with Subversion built in, but if Mercurial has this
as well then I''d say they are about equal in this regard.
>
> the use of cygwin git is a bit problematic, and sometimes eol styles
> mixes don''t like the different interpreters (unix eol against
windows
> eol) with ruby-mswin32 and ruby cygwin.
Yes, git on cygwin is a pain, and is only for the brave. The problem
of Git for Windows users goes away if the main repository is
Subversion.
>
> > With a Subversion repository, you can choose between Subversion as a
> > client or Git as a client (yes, it''s actually a local clone
of the
> > repository, but a client of the main svn repo as well).
> >
> > http://git.or.cz/course/svn.html
> > http://blog.nbwd.co.uk/2007/8/16/using-git-for-rails-development
> >
>
> Again, was talking about that the git-to-svn sync.
http://blog.fallingsnow.net/2007/08/17/maintaining-an-svn-mirror-directly-from-git/
Mercurial can be used by Tailor in the same manner that Evan describes
here, so I''d say they are equal in syncing.
> The git/mercurial over svn without a proper sync solution will be a
> problem for those users using script/plugin to install and use rspec
> on Rails applications -- since rails is highly integrated with svn for
> these commands.
It wouldn''t be a technical problem, as it would be business as usual
for the "script/plugin install" process to pull from Rubyforge svn.
The only problem I see might be a timing issue, but that could be
fixed by sync''ing every commit.
>
> Anyway, just my comments :-)
A fun discussion to have, I think. :) The switch to distributed
version control is a paradigm shift for many, and I''m curious to see
how this one turns out.

There is a msys branch of git that is extremely easy to install in
windows from this url: http://code.google.com/p/msysgit/  I tried it
and it seems to work pretty well

On Nov 19, 2007 2:57 PM, Kevin Williams <kevwil at gmail.com>
wrote:
> On Nov 19, 2007 8:55 AM, Luis Lavena <luislavena at gmail.com> wrote:
> > On Nov 19, 2007 1:21 AM, Kevin Williams <kevwil at gmail.com>
wrote:
> > > On 11/18/07, Luis Lavena <luislavena at gmail.com> wrote:
> > > > On Nov 18, 2007 9:57 PM, Kevin Williams <kevwil at
gmail.com> wrote:
> > > > > I don''t intend to use RSpec source either, but
I suspect the most
> > > > > people would be satisfied with a main Subversion
repository. Git users
> > > > > can check out from / in to a Subversion repository just
fine.
> > > > >
> > > >
> > > > That poses a problem for the poor souls trapped in Windows.
> > >
> > > No it doesn''t. Subversion works great on Windows.
Windows users can
> > > try to use Git in Cygwin if they really want to, but they can
also
> > > just use TortoiseSVN or whatever favorite Subversion client they
want.
> > >
> >
> > I wasn''t talking about the svn clone, was talking about the
sync
> > policy "will be synch''ed one time at day"...
>
> I was suggesting to have only one main Subversion repository rather
> than two different repositories, so there would be no sync. If there
> are two repositories (one Git/Mercurial at EngineYard, one Subversion
> at Rubyforge) then certainly getting the sync right is important.
>
> >
> > That in combination with Git, make difficult to be "out of the
box" useful.
>
> I''m not aware of anything special in Mercurial that would make
this
> easier than Git out of the box. It seems Git would be easier, with
> full two-way sync with Subversion built in, but if Mercurial has this
> as well then I''d say they are about equal in this regard.
>
> >
> > the use of cygwin git is a bit problematic, and sometimes eol styles
> > mixes don''t like the different interpreters (unix eol against
windows
> > eol) with ruby-mswin32 and ruby cygwin.
>
> Yes, git on cygwin is a pain, and is only for the brave. The problem
> of Git for Windows users goes away if the main repository is
> Subversion.
>
> >
> > > With a Subversion repository, you can choose between Subversion
as a
> > > client or Git as a client (yes, it''s actually a local
clone of the
> > > repository, but a client of the main svn repo as well).
> > >
> > > http://git.or.cz/course/svn.html
> > > http://blog.nbwd.co.uk/2007/8/16/using-git-for-rails-development
> > >
> >
> > Again, was talking about that the git-to-svn sync.
>
>
http://blog.fallingsnow.net/2007/08/17/maintaining-an-svn-mirror-directly-from-git/
> Mercurial can be used by Tailor in the same manner that Evan describes
> here, so I''d say they are equal in syncing.
>
> > The git/mercurial over svn without a proper sync solution will be a
> > problem for those users using script/plugin to install and use rspec
> > on Rails applications -- since rails is highly integrated with svn for
> > these commands.
>
> It wouldn''t be a technical problem, as it would be business as
usual
> for the "script/plugin install" process to pull from Rubyforge
svn.
> The only problem I see might be a timing issue, but that could be
> fixed by sync''ing every commit.
>
> >
> > Anyway, just my comments :-)
>
> A fun discussion to have, I think. :) The switch to distributed
> version control is a paradigm shift for many, and I''m curious to
see
> how this one turns out.
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

> There is a msys branch of git that is extremely easy to install in
> windows from this url: http://code.google.com/p/msysgit/  I tried it
> and it seems to work pretty well
>
+1

With this, Git is perfectly usable on Windows now, there is no reason
for not using it on this platform.

On Nov 21, 2007 5:05 PM, Patrick Aljord <patcito at gmail.com>
wrote:
> > There is a msys branch of git that is extremely easy to install in
> > windows from this url: http://code.google.com/p/msysgit/  I tried it
> > and it seems to work pretty well
> >
>
> +1
>
> With this, Git is perfectly usable on Windows now, there is no reason
> for not using it on this platform.
msys means *nix eol (end of line) styles, which sometimes don''t work
quite as expected under ruby-windows.

I commented about this previously. Git don''t over the eol-style
property like svn do (svn:eol-style).

The eol style was discussed on Git list way back, and they said the
SCM shouldn''t care about it :-P
(I agree).

The thing is like I said, with languages like Python or Ruby,
sometimes eol does harm and make things crash.

Anyway, as long there is a up-to-date repository "cross-platform
accessible" I''ll be happy.

-- 
Luis Lavena
Multimedia systems
-
Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi