From james at floehopper.org  Thu Oct 30 05:15:41 2008
From: james at floehopper.org (James Mead)
Date: Thu, 30 Oct 2008 09:15:41 +0000
Subject: [Cruisecontrolrb-developers] JIRA bug reports?
Message-ID: <49097B3D.7080503@floehopper.org>

I have 3 bug reports active in JIRA which don't appear to have had any 
attention. I now notice that you also have a project on Lighthouse.

Which should I use? Also do I need to transfer JIRA bug reports into 
Lighthouse?

I'm particularly concerned with this bug report [1]. We've had to apply 
that patch to make CC.rb work properly.

Thanks, James.

http://blog.floehopper.org

[1] http://jira.public.thoughtworks.org/browse/CCRB-182

From james at floehopper.org  Thu Oct 30 05:16:12 2008
From: james at floehopper.org (James Mead)
Date: Thu, 30 Oct 2008 09:16:12 +0000
Subject: [Cruisecontrolrb-developers] Github or Rubyforge; git or svn?
Message-ID: <49097B5C.3030602@floehopper.org>

Which is the master i.e. which has the latest code?

Thanks, James.

http://blog.floehopper.org

From thewoolleyman at gmail.com  Thu Oct 30 05:30:49 2008
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Thu, 30 Oct 2008 02:30:49 -0700
Subject: [Cruisecontrolrb-developers] Github or Rubyforge; git or svn?
In-Reply-To: <49097B5C.3030602@floehopper.org>
References: <49097B5C.3030602@floehopper.org>
Message-ID: <e3af97510810300230j21a05a7ah3c01e115e7db75de@mail.gmail.com>

On Thu, Oct 30, 2008 at 2:16 AM, James Mead <james at floehopper.org> wrote:

> Which is the master i.e. which has the latest code?
>

I believe the rubyforge repo should be empty, and only contain a pointer to
the github repo

Let us know if that isn't the case...

-- Chad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20081030/5a459acb/attachment.html>

From james at floehopper.org  Thu Oct 30 05:46:53 2008
From: james at floehopper.org (James Mead)
Date: Thu, 30 Oct 2008 09:46:53 +0000
Subject: [Cruisecontrolrb-developers] Github or Rubyforge; git or svn?
In-Reply-To: <e3af97510810300230j21a05a7ah3c01e115e7db75de@mail.gmail.com>
References: <49097B5C.3030602@floehopper.org>
	<e3af97510810300230j21a05a7ah3c01e115e7db75de@mail.gmail.com>
Message-ID: <4909828D.7010605@floehopper.org>

Chad Woolley wrote:
> On Thu, Oct 30, 2008 at 2:16 AM, James Mead <james at floehopper.org 
> <mailto:james at floehopper.org>> wrote:
>
>     Which is the master i.e. which has the latest code?
>
>
> I believe the rubyforge repo should be empty, and only contain a 
> pointer to the github repo
>
> Let us know if that isn't the case...
Hi Chad,

Thanks for the quick reply. You're right the Rubyforge git repos seems 
to just have a single file - moved.txt explaining that it has moved to 
GitHub.

However the Rubyforge svn repos [1] still seems to be available. Can you 
tell me if changes in the GitHub project are being reflected in the svn 
repos or is the GitHub project the only place to get the very latest code?

Thanks, James.
http://blog.floehopper.org

[1] http://cruisecontrolrb.rubyforge.org/svn/

From thewoolleyman at gmail.com  Thu Oct 30 05:53:42 2008
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Thu, 30 Oct 2008 02:53:42 -0700
Subject: [Cruisecontrolrb-developers] Github or Rubyforge; git or svn?
In-Reply-To: <4909828D.7010605@floehopper.org>
References: <49097B5C.3030602@floehopper.org>
	<e3af97510810300230j21a05a7ah3c01e115e7db75de@mail.gmail.com>
	<4909828D.7010605@floehopper.org>
Message-ID: <e3af97510810300253yb8754dbqb40a944a1900d60d@mail.gmail.com>

On Thu, Oct 30, 2008 at 2:46 AM, James Mead <james at floehopper.org> wrote:

>
> However the Rubyforge svn repos [1] still seems to be available. Can you
> tell me if changes in the GitHub project are being reflected in the svn
> repos or is the GitHub project the only place to get the very latest code?
> [1] http://cruisecontrolrb.rubyforge.org/svn/
>

No, I don't think they are maintained.  One of the committers should delete
them (or at least trunk contents) and replace with a pointer to github as
well.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20081030/75d4d498/attachment.html>

From jeremy.lightsmith at gmail.com  Thu Oct 30 13:59:04 2008
From: jeremy.lightsmith at gmail.com (Jeremy Lightsmith)
Date: Thu, 30 Oct 2008 10:59:04 -0700
Subject: [Cruisecontrolrb-developers] changes on lighthouse
Message-ID: <648eacf20810301059v7470ca55y96ad20a61df50c08@mail.gmail.com>

I went ahead and did some much needed reorganization on lighthouse.

I closed out 1.3.  renamed 1.4 to "current", and created a "next" milestone.

our "current" milestone now has what is hopefully the minimum we need to do
to get 1.4 out the door.  mostly updating the website, removing jira and our
svn dir, and a windows path bug...that I don't know too much about.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20081030/3c1944a6/attachment.html>

From jeremy.lightsmith at gmail.com  Thu Oct 30 13:53:15 2008
From: jeremy.lightsmith at gmail.com (Jeremy Lightsmith)
Date: Thu, 30 Oct 2008 10:53:15 -0700
Subject: [Cruisecontrolrb-developers] JIRA bug reports?
In-Reply-To: <49097B3D.7080503@floehopper.org>
References: <49097B3D.7080503@floehopper.org>
Message-ID: <648eacf20810301053x6ba4f3ddg83c6883ff6e91497@mail.gmail.com>

all the bug reports on jira _should_ have been transferred to lighthouse.
however, it looks like this report might have gotten in after the transfer.
it needs to be in lighthouse, that's what we're working off of.

the link to jira should go away when alex updates the website

the best way for you to "cut in line" for this (or any) bug would be to fork
thoughtworks/cruisecontrol.rb on github, make the change on your fork, and
send us a pull request.  as an added bonus, you'll have a working version of
it until we pull your changes.  if your changes are well unit tested and
consistent with our vision of cruise / an obvious bug fix - we'll go ahead
and pull them right away.

otherwise, there may be other things that take priority like getting the
next release out the door.

Jeremy


On Thu, Oct 30, 2008 at 2:15 AM, James Mead <james at floehopper.org> wrote:

> I have 3 bug reports active in JIRA which don't appear to have had any
> attention. I now notice that you also have a project on Lighthouse.
>
> Which should I use? Also do I need to transfer JIRA bug reports into
> Lighthouse?
>
> I'm particularly concerned with this bug report [1]. We've had to apply
> that patch to make CC.rb work properly.
>
> Thanks, James.
>
> http://blog.floehopper.org
>
> [1] http://jira.public.thoughtworks.org/browse/CCRB-182
> _______________________________________________
> Cruisecontrolrb-developers mailing list
> Cruisecontrolrb-developers at rubyforge.org
> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20081030/3dad0329/attachment.html>

From jamesmead44 at gmail.com  Fri Oct 31 05:27:30 2008
From: jamesmead44 at gmail.com (James Mead)
Date: Fri, 31 Oct 2008 09:27:30 +0000
Subject: [Cruisecontrolrb-developers] JIRA bug reports?
In-Reply-To: <648eacf20810301053x6ba4f3ddg83c6883ff6e91497@mail.gmail.com>
References: <49097B3D.7080503@floehopper.org>
	<648eacf20810301053x6ba4f3ddg83c6883ff6e91497@mail.gmail.com>
Message-ID: <1db558f00810310227n2d4e022eg2fe0fddbc9fd0f10@mail.gmail.com>

Thanks. I've now added it to Lighthouse. I'll see if I can find time for a
proper solution to the bug, but pretty busy at the moment so don't hold your
breath.

2008/10/30 Jeremy Lightsmith <jeremy.lightsmith at gmail.com>

> all the bug reports on jira _should_ have been transferred to lighthouse.
> however, it looks like this report might have gotten in after the transfer.
> it needs to be in lighthouse, that's what we're working off of.
>
> the link to jira should go away when alex updates the website
>
> the best way for you to "cut in line" for this (or any) bug would be to
> fork thoughtworks/cruisecontrol.rb on github, make the change on your fork,
> and send us a pull request.  as an added bonus, you'll have a working
> version of it until we pull your changes.  if your changes are well unit
> tested and consistent with our vision of cruise / an obvious bug fix - we'll
> go ahead and pull them right away.
>
> otherwise, there may be other things that take priority like getting the
> next release out the door.
>
> Jeremy
>
>
>
> On Thu, Oct 30, 2008 at 2:15 AM, James Mead <james at floehopper.org> wrote:
>
>> I have 3 bug reports active in JIRA which don't appear to have had any
>> attention. I now notice that you also have a project on Lighthouse.
>>
>> Which should I use? Also do I need to transfer JIRA bug reports into
>> Lighthouse?
>>
>> I'm particularly concerned with this bug report [1]. We've had to apply
>> that patch to make CC.rb work properly.
>>
>> Thanks, James.
>>
>> http://blog.floehopper.org
>>
>> [1] http://jira.public.thoughtworks.org/browse/CCRB-182
>> _______________________________________________
>> Cruisecontrolrb-developers mailing list
>> Cruisecontrolrb-developers at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers
>>
>
>
> _______________________________________________
> Cruisecontrolrb-developers mailing list
> Cruisecontrolrb-developers at rubyforge.org
> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers
>
>


-- 
James.
http://blog.floehopper.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20081031/eeeb8ef4/attachment.html>