I am having a look at the xml serialization and the betwixt issues
(SHINDIG-562), but haven't assigned that blocker to myself yet as I
am not certain I will come up with a fix. As Cassie said, betwixt can
do your head in.
Ian
On 7 Oct 2008, at 01:31, Chris Chabot wrote:
As far as i know the blocker issues are indeed correct (i'll have
to verify
though, i'll save that for tomorrow morning), most of them are
relatively
small though, and better yet, a few of them have patches available
too!
Joseph Smarr's indicated he's still intending to work on the OAuth
support,
but has been doing a bit of a tour around the US (sadly without the
rockstar
style limo's and stuff though i think); But i have hope that will
find it's
way to completion soon (possibly with the help from gonzalo and
ropu, they
both offered)
json-rpc and all that comes with it is very, very close to completion,
together with it's complete clean up of the social interface,
there's the
last 4 or so failing tests in the test suite i would *really* like
to have
fixed before committing so i can be sure it's ready for consumption
(ripping
out working code and replacing it with something new is always
scary, so it
better be a whole lot better!), I had hoped to finish that last
week but
there were some other engagements that kept me otherwise occupied
too, but
this week looks completely open, so that'll be dedicated to the
final push
to finish the social api.
After that it's the other blocker issues that remain, and a few eye
balls
wouldn't hurt either, but all in all I'd say we're *almost* ready
on the php
side of things, I'm hoping to have it all completed and hopefully
reviewed
by everyone within 2 weeks, and ready for release
On Tue, Oct 7, 2008 at 2:03 AM, Kevin Brown <[EMAIL PROTECTED]> wrote:
On Mon, Oct 6, 2008 at 4:39 PM, Dan Peterson
<[EMAIL PROTECTED]> wrote:
Thanks, Kevin.
So what does that mean for the 8 "blocker" issues? It sounds like
some of
those are either not blockers or are resolved but out of date?
They're probably mis categorized.
Chris, would love an update about Shindig PHP if you get a chance :)
-Dan
On Mon, Oct 6, 2008 at 4:31 PM, Kevin Brown <[EMAIL PROTECTED]> wrote:
At this point in time I don't anticipate any major changes in
the java
code base. Chris is still working on several PHP items, and I
don't want
to
do a release without both implementations being in agreement
because we
don't yet know whether the needs of PHP will require changes to the
client
code.
On Mon, Oct 6, 2008 at 2:41 PM, Dan Peterson <[EMAIL PROTECTED]
wrote:
Thanks for the updates.
How are things going?
I see there are currently 8 "blocker" issues -- is that the set of
issues
gating a formal release? If not, can the other issues be added
so we
have
a
clear set of tasks?
-Dan
On Thu, Sep 25, 2008 at 1:08 AM, Chris Chabot <[EMAIL PROTECTED]>
wrote:
On the PHP side of things we have 2 large items still open:
- JSON-RPC
- OAuth support for the REST service
The good news is that these are actively being worked on (Joseph
Smarr
doing
the OAuth bit, and me on JSON-RPC), but the bad news is that with
Joseph
having various engagements in the US, and me doing the Google
Developer
Days
tour in euope, we really can't commit to having that completed in
time
for
a
30th release date. Also keep in mind that since they are
important
and
somewhat sizable components they might need some testing after
being
committed too, so realisticely I think the earliest time I
would be
able to
call it release ready is somewhere around oct 13-17.
There are a few smaller issues in JIRA too, which some great
guys are
working on or even have submitted patches for already, so I
think it
looks
like we'll have those bits covered.
-- Chris
On Wed, Sep 24, 2008 at 2:00 PM, Kevin Brown <[EMAIL PROTECTED]>
wrote:
It's not going to happen by the 30th. Issues are open in
JIRA, but
there's
just far too much work for it to happen in 6 days time.
On Wed, Sep 24, 2008 at 2:45 AM, Dan Peterson <
[EMAIL PROTECTED]>
wrote:
Hey folks,
It's getting close to the proposed Sept 30 release date -- can
folks enumerate the blocking issues in JIRA (they're all
already
in
JIRA,
right?), so all contributors have a clear idea ways in which
they
can
help
out getting to a complete, stable, 0.8.1-compliant release?
Thanks,
-Dan
On Tue, Aug 26, 2008 at 3:20 AM, Kevin Brown <[EMAIL PROTECTED]>
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.
