Did not see any response. Sending out again. I'm hoping people are fine
with branching on 10th.

Thanks
Amareshwari

On Fri, Mar 27, 2015 at 12:04 PM, Amareshwari Sriramdasu <
[email protected]> wrote:

> Hi all,
>
> We have some significant improvements and features added after 2.0
> release, mainly :
>
>
>    - Estimate api and its performance improvement
>    - Partition timeline
>    - DB specific jars and classloaders
>    - API and method timers and metering
>
> and bug fixes.
>
> I'm volunteering to manage the release. I will also make sure to come up
> with how to release doc sothat next release management can be picked by
> someone else.
>
> Calling out for a release preparation for 2.1 here.
>
> Unassigned open items on 2.1 are
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20LENS%20AND%20fixVersion%20%3D%202.1%20AND%20resolution%20%3D%20Unresolved%20AND%20assignee%20is%20EMPTY
> .
> - Contributors are welcome to provide fix for those issues.
>
> All the open issues :
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20LENS%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%202.1
>
> Issues yet to verify :
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20LENS%20AND%20fixVersion%20%3D%202.1%20AND%20status%20%3D%20Resolved&startIndex=50
>
> If any of you feel your changes should go into 2.1 and the jira is not
> marked with fix version, please do so.
>
> Putting down the plan for 2.1 release:
>
>
>    - Will merge master into release branch after two weeks from now.
>    (10/April/2015)
>    - We will spend two week to fix blockers on the release branch if any
>    and verify release candidate. And roll release candidates until a
>    release vote passes(24/April/2015)
>    - Will roll release candidate on 27/April/2015
>
> Let me know your concerns/comments.
>
> Thanks
> Amareshwari
>
>
>
>

Reply via email to