RE: Preparing for REEF 0.11.0 release - cut off line Sun 4/26 12:00pm PST

["Julia Wang (QIUHE)" <Qi...@microsoft.com>]

Here is the plan:

Feature related: Release is a moving train. We don't need to include feature related changes if the feature is still in progress and we cannot complete the at this time. Examples are 
#189 Provide a C# Client API to REEF - Beysim
#227: Add implementation of the REEF Client for HDInsight - Beysim
#154: .NET Group Communication improvements - Julia

Improvements: It is nice to have, but is not a must. 
REEF-69: More fine-grained JVM options control - Brain Cho
REEF-65: Replace retained Evaluator example with the Scheduler - Yunseong - ETA (4/26)

Known issues: User has a workaround. 
REEF-255: Our NuGets don't work upon package restore
REEF-254: Our NuGets don't work upon package update

Blocker: 
All resolved as of now

I  would set 4/26 12:00pm PST as cut off line for branching 0.11 release. 

- If you have any nice to have thing or any half way features you would like to merge before that time, please carefully have a code review and make sure all tests are passed. Please run both java tests and .Net tests. I have updated Wiki for how to run .Net tests. 
- If there is any deprecated API you would like to remove in the next release, please mark them as deprecated/obsolete in 0.11 release so that we can remove them in release 0.12. 
- If you are not comfortable for any changes, don't do last minutes check-in. The next train will come sooner than this time :)

Let me know if you have any concerns or questions.

Thanks,
Julia

-----Original Message-----
From: Markus Weimer [mailto:markus@weimo.de] 
Sent: Thursday, April 23, 2015 9:21 AM
To: REEF Developers Mailinglist
Subject: Re: Preparing for REEF 0.11.0 release

Agreed. We don't need all of the group communications features before we can make a release.

On Wed, Apr 22, 2015 at 10:58 PM, Julia Wang (QIUHE) < Qiuhe.Wang@microsoft.com> wrote:

> REEF-154: It is about .Net Group Communication Improvement. We have 
> completed most of the work items in the list. Some of them are still 
> in progress. I would think we can continue to work on those features 
> in the next release while we are moving on. It is not necessary to 
> have all of those features in the current release. What do you think?
>
> -----Original Message-----
> From: Yunseong Lee [mailto:yunseong.lee0@gmail.com]
> Sent: Wednesday, April 22, 2015 5:38 PM
> To: dev@reef.incubator.apache.org
> Subject: Re: Preparing for REEF 0.11.0 release
>
> Thanks for the great summary!
>
> REEF-65: I could not have spent much time on this issue for a while. 
> I'll finish this no later than 4/26(KST).
>
> Thanks,
> Yunseong
>
> On Thu, Apr 23, 2015 at 9:09 AM, Brian Cho <ch...@gmail.com> wrote:
>
> > Thanks for the summary Markus!
> > REEF-69: I'm working towards a first PR. It might involve some 
> > deprecation so would be nice if I get the changes in on time. But 
> > it's
> not a blocker.
> > -Brian
> >
> >
> >
> >
> >
> >
> > On Wed, Apr 22, 2015 at 8:19 AM -0700, "Markus Weimer"
> > <ma...@weimo.de>
> > wrote:
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Hi,
> >
> > I just did a pass through our open issues list and found a few I 
> > believe we should address before a release. I marked all of them as 
> > blocking
> > REEF-147:
> >
> >   * REEF-235: We have a secret key in the code base.
> >   * REEF-255: Our NuGets don't work upon package restore.
> >   * REEF-254: Our NuGets don't work upon package update.
> >   * REEF-195: Our NuGets and DLLs don't have the same version.
> >
> > REEF-235 should be an easy fix.
> >
> > 254 and 255 can be marked as "known issues" in the release notes, if 
> > we can't fix them in time. They both have a workaround in 
> > uninstalling and re-installing the NuGets.
> >
> > 195 could create problems for our next release, as the DLLs then 
> > would have lower version numbers than right now. Maybe an easy 
> > hotfix would be to manually set all their versions to 0.11 for now, 
> > and solve the sync between NuGet and DLL version for 0.12. If so, we 
> > should file two subtasks for that, and mark them as blocking for the 
> > appropriate release JIRA.
> >
> > Also, looking at JIRA, the following issues are marked as "In Progress".
> > It would be good to get a quick round of feedback from the people 
> > they are assigned to:
> >
> >   * REEF-69: Brian
> >   * REEF-189 and REEF-227: Beysim
> >   * REEF-154: Juliua
> >   * REEF-65: Yunseong
> >
> > Thanks,
> >
> > Markus
> >
>