Assuming we are still going for a June 15th release date (approximate), I wanted to make sure the community is in agreement with what will be in scope. The following are the release notes prepared from JIRA. Any issues that are not yet resolved are noted with a -- prefix
Release Notes - Rave - Version 0.1-INCUBATING ** Technical task * [RAVE-14] - Create basic object model to support rendering of widgets * [RAVE-15] - Implement basic JPA persistence layer * [RAVE-16] - Create basic page rendering * [RAVE-17] - Implement OpenSocial/Shindig Common Container * [RAVE-18] - Implement basic user logon features * [RAVE-19] - Add gadget container-side hooks --* [RAVE-20] - Implement container/shindig auth --* [RAVE-27] - Implement User Prefs ** Story --* [RAVE-12] - Render OpenSocial Gadgets on Page in iFrames --* [RAVE-30] - Render W3C widgets on Page in iFrames * [RAVE-32] - Create basic widget repository * [RAVE-33] - Create the ability to move widgets on a page We nee our mentors to help us through this process, but I *think* we need the following before release: * Finish outstanding issues or pull them out of scope for release * Issue verification & closure (testing) * License marking verification * Dependency verification * IP verification * Wire up nexus for artifact release * Hold a community vote * Hold an IPMC vote I plan on taking on the container/shindig auth piece next week, Jesse is currently working on user prefs, and Ross is working on implementing the call to Wookie to get the iFrame URL for the given context. I think if we don't have these issues completed by end of next week, we should pull them from the 0.1 release and move forward. We will need to get volunteers to test the various issues. As we agreed earlier, it is best if the person implementing the issue doesn't test/close the issue. As for the IPMC & license tasks, I don't know what our first steps are supposed to be (although I am sure there is a guide I need to read). Thoughts? -Matt
