I will be working on the release now. Please hold off any commits until you see the vote thread.
Initially I was debating on releasing from trunk, but looking at Saminda's refactoring email, just to be safe I will branch 0.3-incubating-snapshot and then proceed with the release. Hi Lahiru, I saw a commit from you which breaks Jenkins build because of a missing java jar, weird. I looked through your commit and it does not effect 0.3 features. Excuse me but I will skip your last commit for the release. Suresh On May 14, 2012, at 10:30 AM, Suresh Marru wrote: > I went through the build and tutorials and everything seems to be good. We > have decent improvements and bug fixes in 0.3 release [1]. We have much more > in 0.4 release [2] but that will require significant testing to make sure all > these release features work well. Any objections on pushing out a 0.3 > release today evening? > > Suresh > > [1] - > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311302&version=12318556 > [2] - > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311302&version=12318557 > On May 1, 2012, at 10:30 AM, Suresh Marru wrote: > >> Hi All, >> >> Since the trunk moved too further along since 0.2 branching, how about we do >> a release of 0.3-incubating ASAP? If we see any issues with 0.2 during IPMC >> vote, we have to re-align. >> >> Here are the current release notes as of today - >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311302&version=12318556. >> Along with addressing the comments on current release and further improving >> NOTICE file, I see two major tasks before we proceed with the release: >> >> * Merge changes in 0.2 branch to trunk and remove 0.2 branch. >> * Have the release documentation on Wiki. >> >> As soon as get the 0.3-incubating release wrapped up, we should start a >> detailed feature discussion with current and roadmap and discuss subsequent >> release plans. Thoughts? >> >> Suresh >> >> On Feb 6, 2012, at 10:01 AM, Suresh Marru wrote: >> >>> Hi All, >>> >>> While we working through release semantics on the 0.2-incubating-snapshot >>> branch, the trunk moved quite significantly. Great job from every one in >>> marching ahead. I think we are in a good position for an immediate >>> 0.3-incubating release. Any thoughts or objections to this plan? >>> >>> I see the following feature additions since 0.2 is branched in december: >>> >>> * Grid submissions to supercomputers are now working for basic >>> applications. >>> * Registry and workflow launching now have cool API's so web interfaces can >>> be built against. >>> * User interface have been improved but this looks like work in progress. >>> * Workflows now have For-Each iterative support, looks like there are open >>> tickets on this issues, but workable within this week. >>> * Registry is now persisting state information from workflow launches and >>> progress >>> * Workflows have provenance aware capabilities so the execution begins from >>> the mid workflow where data is available. >>> >>> Please add/modify to the list, but I see these are significant improvements >>> mandating a release. I propose the following release preparation for 0.3: >>> * Since there are enough features already call a feature freeze immediately. >>> * Wrap up any changes to these features, test document and make a code >>> freeze by Friday 02/10 >>> * Make a release over next weekend. >>> >>> This plan assumes the current voting 0.2 release goes through. If we find >>> blockers in 0.2, I still suggest to stick to 0.3 release plan, branch it >>> and let the trunk move forward. I am getting bothered with trunk advancing >>> too much without a release. >>> >>> Thoughts? >>> >>> Cheers, >>> Suresh >> >
