Yes, but hopefully for much less than that period.


Sent via a mobile device. Please excuse typos or brevity.

 -----Original Message-----
From:   Marlon Pierce [mailto:[email protected]]
Sent:   Monday, July 25, 2011 04:09 PM Eastern Standard Time
To:     [email protected]
Subject:        Re: 0.2-incubating Release

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Matt--

Just to confirm--we should freeze SVN commits from end of the day Thursday 
until end of the day Friday?


Thanks--


Marlon


On 7/25/11 3:12 PM, Franklin, Matthew B. wrote:
> It's that time again, we are going for another Rave release! (expected
> groans and boos)  As we discussed earlier, releasing on a monthly cadence
> should help ensure we are driving (quickly) toward a stable graduation
> release.  I currently have the release scheduled for the 31st of this
> month (Sunday), and future releases scheduled for the end of each month.
> Since we went through this once before, this process will hopefully be a
> little less difficult to manage (and take less time).
> 
> Below are the current release notes that were generated by JIRA for the
> 0.2-INCUBATING release.  There are still a bunch of open issues (denoted
> by a -- prefix).  If you are working on one of the open issues, please
> update its status to resolved if it is completed, or move it to
> 0.3-INCUBATING if it is not completed.
> 
> Unless anyone objects to releasing, I will move any open issues not closed
> by the end of the day Thursday to 0.3-INCUBATING and begin the release
> process Friday.
> 
> To ensure that we don¹t shutdown trunk development for too long, I will be
> sure to complete the initial release steps (creating the tag and
> artifacts) by the end of Friday.  If something major is found, we will
> cancel the release and fix it in 0.3-INCUBATING.
> 
> 
> Release Notes - Rave - Version 0.2-INCUBATING
> 
> ** Sub-task
>     * [RAVE-36] - Need RAVE-styled login, signup pages
>     * [RAVE-39] - Need to provide skeleton for CSS and tag libraries
>     * [RAVE-40] - Write Jasmine unit tests for W3C Widget JavaScript
> libraries.
>     * [RAVE-44] - Need message display to user confirming widget addition
> from repository
>     * [RAVE-79] - Move the inline scripts for rendering the gadgets
>     * [RAVE-83] - Provide a way to override properties from
> shindig.properties
> -- * [RAVE-84] - Oauth key and secrets need to be maintainable (and secure)
> -- * [RAVE-85] - Persistent OAuth request tokens
>     * [RAVE-106] - Enhance RegionWidget model to support storing
> RegionWidgetPreference's
>     * [RAVE-107] - Create REST API for persisting RegionWidget preferences
>     * [RAVE-108] - Add the metadata required to dynamically generate the
> preferences UI on the client side into the widget object
>     * [RAVE-109] - Add preferences button to gadget chrome bar which
> generates the UI for editing preferences onclick
>     * [RAVE-110] - Implement save/cancel handlers for edit prefs UI which
> use the REST api to persist preferences and re-render the widget with the
> updated preferences
> -- * [RAVE-111] - Implement proper error checking for "required" userprefs
> -- * [RAVE-112] - Figure out how to get the current view and re-render in
> the current view instead of defaulting to the home view when preferecnes
> are saved
> -- * [RAVE-113] - Implement container side support for set_pref
> gadgets.rpc call
> -- * [RAVE-114] - Add security to RegionWidgetService to ensure users can
> only update preferences for RegionWidgets which they own
>     * [RAVE-115] - Dont show the edit preferences button if the gadget
> does not have any user-editable preferences (either no prefs or all hidden)
> 
> ** Technical task
> -- * [RAVE-35] - Implement Person related SPIs
>     * [RAVE-119] - Create Rave Commons Project
>     * [RAVE-120] - Move common components of Rave-Portal/Rave-Shindig to
> Rave-commons
> -- * [RAVE-121] - Add Spring Integration to Rave-Shindig
> -- * [RAVE-122] - Implement Person Service as Example of pattern
> 
> ** Bug
>     * [RAVE-58] - Refactor Delete
>     * [RAVE-78] - rave-shindig incorrect dependency scope on
> shindig-social-api pulls in el-api jar breaking JSPs
>     * [RAVE-86] - Drag and drop error for widgets in IE 9
>     * [RAVE-88] - Gadgets don't render when JavaScript console is not
> available
> -- * [RAVE-117] - "Widget Store" and "Logout" links are disabled when a
> gadget is in canvas view.
> 
> ** Improvement
>     * [RAVE-45] - Portal host/ip configuration (Non-localhost support)
>     * [RAVE-65] - Add JRebel configuration to the documentation and split
> up 'source code' page
>     * [RAVE-87] - Move javaagent property to parent pom
>     * [RAVE-91] - CSS and layout updates
> -- * [RAVE-94] - Update donated UI
> 
> ** New Feature
> -- * [RAVE-20] - Implement container/shindig auth
> -- * [RAVE-89] - Provide basic new user registration feature
> 
> ** Story
> -- * [RAVE-27] - Implement User Prefs
> -- * [RAVE-30] - Render W3C widgets on Page in iFrames
>     * [RAVE-53] - Need to add support for canvas views, canvas/home view
> toggling
> -- * [RAVE-62] - Create a common project and apply common patterns to both
> rave-portal and rave-shindig
> -- * [RAVE-101] - Authorize RPC oeprations on the page
> 
> ** Task
>     * [RAVE-98] - Start documentation section on website
>     * [RAVE-104] - Update version in Reactor pom
> 
> ** Umbrella
> -- * [RAVE-80] - Fix TODO's
> -- * [RAVE-82] - OAuth persistent implementation
> 
>   
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOLc1LAAoJEEfVXEODPFID/SAH/3r8BZI1DJeDETAKiIJanaVC
fvWAsOAMtlXy7kmhEWq3DQxDvIcyKWjNaJ7YUVSqsDxnfyC0c1B/9nsD0LM4ezU8
SolIXrs50s7sAqZe+/hfE32gTdWASaswtyYG+QNyic5YNods6TINAXyNuVk8EpOD
eQWCYQTZbS0eP9sXnkI9bvIGy9CDyjfncKS9R47gIYwglfT58OB+qTg6ARKF0M8B
gxgUCzJW3tuem2GlwP8mNAIXEkmNaW4a2k5ZJ6/Hs9E/dGWvZclTm6CUSjXBdGGP
LSANtwLs+5SDxvLgQM1lEIR93thsHUZItkSTROejQfksRckHpQjCbRl2OjncpL4=
=uder
-----END PGP SIGNATURE-----

Reply via email to