If issues marked for 2.0 are not resolved by suggested date, they will be moved to next release unless they are blockers.
Thanks Amareshwari On Wed, Jan 14, 2015 at 10:24 AM, amareshwarisr . <[email protected]> wrote: > Hello Lens contributors, > > Thinking about the first release after incubating into apache, I volunteer > for managing release 2.0. > > Here are all the issues marked for release - > https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%202.0%20AND%20project%20%3D%20LENS > . > > Issues still open - > https://issues.apache.org/jira/issues/?jql=project%20%3D%20LENS%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%202.0 > > Issues yet to verify - > https://issues.apache.org/jira/issues/?jql=project%20%3D%20LENS%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20%3D%202.0 > > - Once the issue is verified, the issue will be CLOSED and regression > added to regression suite. We don't have regression suite available in code > base yet. Arshad and Raghavendra from Inmobi volunteered to put this up. > > If any of you feel your changes should go into 2.0 and the jira is not > marked with fix version, please do so. > > Putting down the plan for 2.0 release: > > > - Will merge master into release branch after two weeks from now. > (28/01/2015) > - We will spend one week to fix blockers on the release branch if any > and verify release candidate. And roll release candidates until a > release vote passes(04/02/2015) > - Will roll release candidate on 05/02/2015 > > Let me know your concerns/comments regarding the process or dates > > Thanks > Amareshwari >
