shindig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan J Baxter" <>
Subject RE: Shindig 3.0 timeline
Date Wed, 25 Jan 2012 02:51:55 GMT
Ilya, if you or Dennis want to investigate and come up with a patch to 
support this use case, we are happy to accept it :)  Everyone on the dev 
list would be happy to help you or anyone else through the process of 
writing the patch and getting it committed.


Software Engineer - OpenSocial
IBM Collaboration Solutions

Phone: 1-978-899-3041
Chat: rbaxter85 ryanjasonbaxter 
Find me on:      and within IBM on:  

550 King St
Littleton, MA 01460-1250
United States

From:   "Shtein, Ilya" <>
To:     "" <>, 
Date:   01/20/2012 10:12 AM
Subject:        RE: Shindig 3.0 timeline

Any chance SHINDIG-1497 will be fixed in 3.0.0 ( How can a new version 
be released with such an important feature (pubsub-2) in a broken state? I 
am not allowed to contribute, but will be happy to provide information to 
anyone who is willing to work on it.


-----Original Message-----
From: Paul Lindner [] 
Sent: Friday, January 20, 2012 8:55 AM
Subject: Re: Shindig 3.0 timeline

I'm not keen on version numbers myself.

We can release at any time really, code is stable, tests are all green.

If someone wants to sign up to do maint releases of 3.0.x that would be 

  Release current trunk as shindig-3.0.0, move trunk to 3.1.0-SNAPSHOT

  [  ] +1 do it
  [  ] +0 meh
  [  ] -1 I have just one more patch.

If you do -1 please provide code-review links or jira issues you consider 
blockers for 3.0.0

On Fri, Jan 20, 2012 at 3:51 AM, Derek Houghton <> 

> Hi,
> Didn't catch a reply to this?
> Could you tell me when stable shindig 3.0 is due for public release?
> Thanks
> Derek
> On 16 Jan 2012, at 10:57, Evgeny Bogdanov wrote:
> > Hello,
> >
> > when the shindig 3.0 is due?
> >
> > Best
> > Evgeny

Paul Lindner -- --

The information contained in this message is proprietary and/or 
confidential. If you are not the intended recipient, please: (i) delete 
the message and all copies; (ii) do not disclose, distribute or use the 
message in any manner; and (iii) notify the sender immediately. In 
addition, please be aware that any message addressed to our domain is 
subject to archiving and review by persons other than the intended 
recipient. Thank you.

  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message