You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@shindig.apache.org by Stanton Sievers <ss...@apache.org> on 2013/10/14 17:08:47 UTC

Proposing SHINDIG-1938 for 2.5.0-Update1

Hi everyone,

I was looking at upgrading Rave to Shindig 2.5.0 and ran into what looks
like an oversight when app data was updated as part of SHINDIG-1916 [1].

I created SHINDIG-1938 [2] to address the issue and have a patch available
[3].

I think this is something we should get into Update1 if at all possible
since the fix that went into 2.5.0 for app data updates was incomplete.

The current patch is for trunk, but I can easily port it to 2.5.0-update1.

Thanks,
-Stanton

[1] https://issues.apache.org/jira/browse/SHINDIG-1916
[2] https://issues.apache.org/jira/browse/SHINDIG-1938
[3] https://reviews.apache.org/r/14629/

Re: Proposing SHINDIG-1938 for 2.5.0-Update1

Posted by Ryan Baxter <rb...@apache.org>.

+1 sounds good to me

On Mon, Oct 14, 2013 at 11:08 AM, Stanton Sievers <ss...@apache.org> wrote:
> Hi everyone,
>
> I was looking at upgrading Rave to Shindig 2.5.0 and ran into what looks
> like an oversight when app data was updated as part of SHINDIG-1916 [1].
>
> I created SHINDIG-1938 [2] to address the issue and have a patch available
> [3].
>
> I think this is something we should get into Update1 if at all possible
> since the fix that went into 2.5.0 for app data updates was incomplete.
>
> The current patch is for trunk, but I can easily port it to 2.5.0-update1.
>
> Thanks,
> -Stanton
>
> [1] https://issues.apache.org/jira/browse/SHINDIG-1916
> [2] https://issues.apache.org/jira/browse/SHINDIG-1938
> [3] https://reviews.apache.org/r/14629/