I have some rough edges that I am happy to take on and some questions
about the some surrounding things, that might be too late for the
release.
Rough Edges,
There are places where Javadoc is lacking on java interfaces
especially, I was working my way though that but I got interrupted by
a holiday, but happy to fix, if its felt important.
Surrounding.
I have a number of Cache implementations looking for a Home (small) and
I have a 80% complete relational DB implementation of the SPI's in
the Social layer looking for a Home (larger)
Are these 2 too late for the 1.0 Release ?
and a more general question.
Do we want Shindig to come out of the box as a functioning RI or is
it a set of Jars that would need extra work to turn into a
functioning RI.
By functioning, I mean a RI that could support a small number of
users in production, rather like Jackrabbit can.
I wouldn't want any of this to delay the release.
Ian
On 26 Aug 2008, at 11:20, Kevin Brown wrote:
Hi everyone,
We've been saying for a while that 0.8 completion was a
prerequisite for our
first release. As we approach this milestone, it's time to really get
serious about it.
To make this happen, we're going to need to do the following:
1. Lock down all public interfaces and signatures. This is critical
if we
want to be able to offer any compatibility guarantees.
2. Get rid of rough edges. Now is the time to resolve any outstanding
integration issues.
3. Lock down a target release date. September 30th gets my vote,
but I'm
willing to hear arguments otherwise.
We can lock down the release into distinct components, as long as
compatibility guarantees are met, but we should strive to release
everything
at around the same time so as to avoid developer confusion.
There are 5 major components that need to be released:
- javascript (all together, due to interdependencies)
- Java/PHP social data component
- Java/PHP gadget rendering component
I'm not that concerned about the java web app artifact, but that
wouldn't
hurt either.
