I'm planning to merge the patch into the trunk within the next days (i
hope nothing goes wrong). That would mean it will be released with
1.5. We have a feature freeze for 1.4.4, which will be the last 1.4
release i guess... I hope 1.5 is still early enough for you.

The source for the feature is available already. Have a look into
CCNET-1188 [1]. If you try it be sure to tell us about your
experience.

I hope that's what you wanted to hear. Sorry that i didn't merge it
earlier, but i have very limited resources right now. :-)

regards,

Daniel

[1] http://jira.public.thoughtworks.org/browse/CCNET-1188


2009/5/6 Rich <[email protected]>:
>
> Do you have a rev of 1.4 earmarked yet for merging mercurial support?
> I'm converting my first project to mercurial next week and was hoping
> to get an idea of when the source might be available.  Thanks.
> --Rich
>
> On Apr 8, 8:54 am, Rich <[email protected]> wrote:
>> Thank you.  That is great news.
>>
>> On Apr 8, 1:10 am, Daniel Hommel <[email protected]> wrote:
>>
>> > Hi Rich,
>>
>> > a patch formercurialsupport has been contributed but it didn't make
>> > it into the 1.4.3 release. Right now i'm planning to merge it before
>> > the 1.5 release. I hope that's what you wanted to know.
>>
>> > regards,
>>
>> > Daniel
>>
>> > On Tue, 7 Apr 2009 13:48:54 -0700 (PDT)
>>
>> > Rich <[email protected]> wrote:
>>
>> > > I have only been using CruiseControl.NET for about 6 weeks and I love
>> > > it.  I have been working with MSBuild projects in SVN but we are
>> > > looking to move toMercurialand I don't see a Source Control Block
>> > > forMercurialin the documentation.  Is the External Source Control
>> > > block meant to be used in an instance like this where there is no
>> > > explicit control block for your SCM system?  Has anyone used
>> > > CruiseControl.NET withMercurial?
>>
>> > > BTW - I see that the licensed Cruise product and the SourceForge
>> > > CruiseControl project both have explicit support forMercurialand I
>> > > am looking at those, but I would prefer to stay with CC.NET.

Reply via email to