Hi Saminda, Great. So please goahead and start with the process, here are some handy steps:
1) Digest the latest developments and send out a feature list for this list. Once a consensus on release features is reached, post them on the website [1] (I just realized its way outdated, we need to update it with current and future releases). 2) Go through the JIRA's and appropriately tag the release 'Fix Version' for the upcoming release 3) Set a target date for a feature freeze and engage dev list in closing or deferring the issues. 4) Call out for a testing period and when you are comfortable, freeze the trunk for a short time and go through the release process. Note: Last two releases we branched and then released mainly because I wanted to focus on the build and legal issues (L, N, D) and did not want to stall development. You need not do it this time as we have the build and L, N files in a much better shape. Suresh [1] - http://incubator.apache.org/airavata/development/roadmap.html On Jun 18, 2012, at 12:39 PM, Saminda Wijeratne wrote: > WIll do Suresh. I will go through the existing jiras & prioritize... > > Saminda > > On Mon, Jun 18, 2012 at 7:40 AM, Suresh Marru <sma...@apache.org> wrote: > >> Hi All, >> >> With an anticipation for 0.3-incubating release, we need to start making >> 0.4-incubating release plans. I see the following open JIRA's tagged for >> 0.4 - http://s.apache.org/hQ. >> >> I build files and release process is much streamlined now, I also cloned >> Rave release instructions and updated for Airavata - >> http://incubator.apache.org/airavata/development/release-management.html. >> How about we rotate the release managers? I will be happy to hand hold the >> release process if others would like to step in. >> >> Saminda, >> >> As I look through, the commits we had since branching 0.3, major >> development seems to be XBaya refactoring. Since you steered these changes, >> will you be able to be RM for this release? I can work with you on the >> process and we can update the release documentation as we go along. >> >> Suresh >>
signature.asc
Description: Message signed with OpenPGP using GPGMail
