Great, thanks Amareshwari !
Do you need any help to cut off the release now ?
Thanks again,
Regards
JB
On 04/16/2015 12:20 PM, amareshwarisr . wrote:
Merged master into release branch. And moved master to next development
version 2.2.
Thanks
Amareshwari
On Wed, Apr 15, 2015 at 7:26 AM, amareshwarisr . <[email protected]>
wrote:
I'm facing some issues while merging master into release-line with respect
to conflicts. Will update once fixed.
Thanks
Amareshwari
On Wed, Apr 15, 2015 at 6:20 AM, Jean-Baptiste Onofré <[email protected]>
wrote:
+1
Regards
JB
On 04/15/2015 12:46 PM, amareshwarisr . wrote:
Hi all,
Planning to merge master into release branch today.
All the issues still marked for 2.1 release are only doc or test issues.
The only code changes we would merge are LENS-499, as examples are
failing
right now.
Thanks
Amareshwari
On Thu, Apr 9, 2015 at 1:10 AM, Jean-Baptiste Onofré <[email protected]>
wrote:
Hi Amareshwari
let me take some, but we need definitely some help there.
Regards
JB
On 04/09/2015 08:04 AM, amareshwarisr . wrote:
Seeing huge number of issues still open :
Open : 49
In progress : 5
Patch available : 2
Will wait for branching till early-mid next week - mostly 14th or 15th.
Not
moving the verifying and rolling candidate date from 24th and 27th.
Let us know comments or concerns.
Thanks
Amareshwari
On Tue, Mar 31, 2015 at 5:53 PM, Jean-Baptiste Onofré <[email protected]
wrote:
Hi,
I thought I replied to this e-mail. +1 for that.
I will assign some Jira to me in order to move forward.
Regards
JB
On 03/27/2015 07:34 AM, Amareshwari Sriramdasu 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
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
