I would like to see the 1.0 go into a release, but just at the moment
I probably dont have enough time to go through the process (alone)
SHINDIG-776
Was talked on list, I think the view expressed by other committers was
that jslint produces a lots of warnings that may not be relevant, that
view, if widely held should be synchronized with the issue and the
appropriate action taken ( probably wont fix on the branch)
SHINDIG-560
A merge is required from trunk as the version of the patch committed
to the 1.0.x is before it was reworked by Adam removing some major
issues with the earlier version.
SHINDIG-803
Would probably apply, but I wonder what the support for hasFeature is
like in trunk ? Anyone ?
SHINDIG-907
Should be quite easy to apply.
If I get a moment I will try and pull them into the branch.
Has anyone looked at the readiness of the jars for a release ?
Ian
On 16 Mar 2009, at 21:23, Tim Moore wrote:
Has there been any more discussion about releasing from the 1.0
branch?
There is one unresolved issue with a fix version of 1.0.0-rc1:
http://issues.apache.org/jira/browse/SHINDIG-776
and one with a fix version of 1.0.x-incubating:
http://issues.apache.org/jira/browse/SHINDIG-560
Neither of those have seen much activity recently.
There are other open issues with no target fix version that should
perhaps be considered for the branch (e.g., http://issues.apache.org/jira/browse/SHINDIG-803)
, and others that have been fixed on trunk already that should
probably be merged to the branch if possible (e.g., https://issues.apache.org/jira/browse/SHINDIG-907)
but I haven't gone through the issues exhaustively.
Are the committers still interested in making a 1.0 release? What's
preventing that from happening right now, and what's the best way
that we non-committers can help progress this?
On Oct 31, 2008, at 7:13 PM, 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!
--
Tim Moore
