You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by Bernd Fondermann <bf...@brainlounge.de> on 2009/06/08 18:07:06 UTC

[vysper][pubsub] Pending patches

Hi Michael,

can you give me a hand, which patches I should review now?

I'm back from my break and will incorporate your code over the next days.

Sorry and Thanks,

   Bernd

Re: [vysper][pubsub] Pending patches

Posted by Bernd Fondermann <bf...@brainlounge.de>.
Done.

 Bernd

Michael Jakl wrote:
> Hi!
> 
> On Mon, Jun 8, 2009 at 18:07, Bernd Fondermann<bf...@brainlounge.de> wrote:
>> can you give me a hand, which patches I should review now?
>>
>> I'm back from my break and will incorporate your code over the next days.
> 
> No problem:
> 
> VYSPER-54.1.patch is the combined patch for unsubscribe and publish
> (that is, it contains the patch from VYSPER-53).
> VYSPER-64.1.patch deals with refactoring the model classes towards
> persistence providers (as in other modules). I've generated that patch
> on top of VYSPER-54.1.patch, I hope this works? Be warned, the
> transition isn't complete... .
> 
> Here the related issues:
> https://issues.apache.org/jira/browse/VYSPER-53 (nothing to apply here)
> https://issues.apache.org/jira/browse/VYSPER-54 (apply first)
> https://issues.apache.org/jira/browse/VYSPER-64 (apply second)
> 
> After completing the transition to persistence providers (in-memory at
> first), I'd deal with the error cases of the use-cases I already
> implemented.
> 
> Michael
> 


Re: [vysper][pubsub] Pending patches

Posted by Michael Jakl <ja...@gmail.com>.
Hi!

On Mon, Jun 8, 2009 at 18:07, Bernd Fondermann<bf...@brainlounge.de> wrote:
> can you give me a hand, which patches I should review now?
>
> I'm back from my break and will incorporate your code over the next days.

No problem:

VYSPER-54.1.patch is the combined patch for unsubscribe and publish
(that is, it contains the patch from VYSPER-53).
VYSPER-64.1.patch deals with refactoring the model classes towards
persistence providers (as in other modules). I've generated that patch
on top of VYSPER-54.1.patch, I hope this works? Be warned, the
transition isn't complete... .

Here the related issues:
https://issues.apache.org/jira/browse/VYSPER-53 (nothing to apply here)
https://issues.apache.org/jira/browse/VYSPER-54 (apply first)
https://issues.apache.org/jira/browse/VYSPER-64 (apply second)

After completing the transition to persistence providers (in-memory at
first), I'd deal with the error cases of the use-cases I already
implemented.

Michael