All the java social issues are in jira and marked as blockers. As of right now it looks like there are 7 blockers (I just went through the list today to clean things up): 621, 601, 562, 561, 560, 559, 497 Does anybody know of any java social issues that are not filed? Or think that the blocking/non-blocking status needs to be modified?
- Cassie On Tue, Sep 23, 2008 at 5:45 PM, 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. > > >
