RippleRestoreTask part of Ripple

[danielmarbach]

Would it be possible to make

https://github.com/Particular/RippleRestoreTask

part of ripple? Or at least point the documentation to the task? I think it is really handy.

[danielmarbach]

Any updates on this?

[jmarnold]

We need to consolidate the changes from ripple v3. I'm targeting next Friday (January 10th) as the tentative release for ripple 3. Once that's settled, we can more easily work this in.

The task itself wasn't the issue, if I call correctly. It was an issue of how the NServiceBus guys needed the ripple mode detection to work (along with the discovery of the ripple.config file). I believe we just about have that sorted out now.

I'll let @andreasohlund or @SimonCropp chime in on that one.

[danielmarbach]

If I remember correctly this has nothing todo with the msbuild task. Andreas and Simon did monkeypatch (sorry guys couldn't resist ;)) their fork of ripple. The task is seperate.

Am 30.12.2013 um 15:44 schrieb Josh Arnold [email protected]:

We need to consolidate the changes from ripple v3. I'm targeting next Friday (January 10th) as the tentative release for ripple 3. Once that's settled, we can more easily work this in.

The task itself wasn't the issue, if I call correctly. It was an issue of how the NServiceBus guys needed the ripple mode detection to work (along with the discovery of the ripple.config file). I believe we just about have that sorted out now.

I'll let @andreasohlund or @SimonCropp chime in on that one.

—
Reply to this email directly or view it on GitHub.

[andreasohlund]

Correct, the "auto downgrade stability to released only if not on develop branch" is a separate thing

Sent from my iPhone

On 30 dec 2013, at 16:33, danielmarbach [email protected] wrote:

If I remember correctly this has nothing todo with the msbuild task. Andreas and Simon did monkeypatch (sorry guys couldn't resist ;)) their fork of ripple. The task is seperate.

Am 30.12.2013 um 15:44 schrieb Josh Arnold [email protected]:

We need to consolidate the changes from ripple v3. I'm targeting next Friday (January 10th) as the tentative release for ripple 3. Once that's settled, we can more easily work this in.

The task itself wasn't the issue, if I call correctly. It was an issue of how the NServiceBus guys needed the ripple mode detection to work (along with the discovery of the ripple.config file). I believe we just about have that sorted out now.

I'll let @andreasohlund or @SimonCropp chime in on that one.

—
Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub.