I am ok for a branch, it would be good to check how the release is going to be done with the mix of java and php, as I would assume this wont just be a tarball of the source tree ?

Some blocker issues
------------------------
I have a minor concern and some advice needed on SHINDIG-562, which is the blocker on the XML format for the RPC interface.

There were a reasonable number of issues/bugs in the XSD that was released for 0.8.1 in the spec. These will be fixed in 0.9, but if I implement to the 0.8.1 it will change on the next release and wont be backwards compatible.

I could take what I think the XSD for 0.9 would look like... but thats not final, and this will need to replace the BeanXmlConverter and BeanAtomConverter beans that are currently wired in. There is a new XStream based converter that is lighter, faster and easier to use that would replace these 2 but is not currently wired into the module.

Options:
1. Make SHINDIG-562 major and don't deliver compliant XML in the release.
2. Deliver to the 0.8.1 XSD as stands and expect to see major change
3. Deliver to a very early draft of the 0.9 XSD and expect some minor fixes.

I would like to do 3, but that might be premature.
---------------------

SHINDIG-561, SHINDIG-497 both blockers will be easy once 562 is fixed.
---------------------



Ian

On 1 Nov 2008, at 02:13, Kevin Brown wrote:

Hi everybody,

We've sort of waffled on release for a while now, and I'd like to get the ball rolling again. Things seem pretty stable right now, but if we don't move to get a release the spec process is going to make releasing soon very
difficult.

So lets lock down and get released.

We're pretty much fully 0.8.1 compliant (barring a few minor issues). We have some of the 0.9 stuff already implemented, but we should not consider
that "advertised" yet until it's really finalized and developers start
expecting it.

So, where do we stand? Can everyone agree on a branch and release two weeks
from now?

I'd like this to be the "1.0" release, with the next release including
support for opensocial 0.9. I don't feel that it's a good idea to align our versions with the specifications versions, but we should include something in our version string or release notes that makes compatibility obvious.

Shindig will be 1 year old on December 12th (well, it's technically a few
weeks older than that but that's the oldest commit I can find in SVN).
Surely we can get a release out before then!

Reply via email to