The vote has passed; I’ve marked some bugs fixed for 2.1 to target 2.0.1
and backported a few patches.
Please mark any bug fixes in progress that you think should be in 2.0.1,
for 2.0.1.
On 16/3/31, 22:58, "Carl Steinbach" wrote:
>+1
>
>On Thu, Mar 31, 2016 at 9:06 PM, Prasanth J
>wrote:
>
>> +
+1
On Thu, Mar 31, 2016 at 9:06 PM, Prasanth J wrote:
> +1
>
> Thanks
> Prasanth
> > On Mar 31, 2016, at 5:37 PM, Lefty Leverenz
> wrote:
> >
> > +1
> >
> > -- Lefty
> >
> > On Thu, Mar 31, 2016 at 4:55 PM, Thejas Nair
> wrote:
> >
> >> +1
> >>
> >> On Thu, Mar 31, 2016 at 1:20 PM, Sergey Shel
+1
Thanks
Prasanth
> On Mar 31, 2016, at 5:37 PM, Lefty Leverenz wrote:
>
> +1
>
> -- Lefty
>
> On Thu, Mar 31, 2016 at 4:55 PM, Thejas Nair wrote:
>
>> +1
>>
>> On Thu, Mar 31, 2016 at 1:20 PM, Sergey Shelukhin
>> wrote:
>>> There have been a few bug fixes since 2.0, some more might be in
+1
-- Lefty
On Thu, Mar 31, 2016 at 4:55 PM, Thejas Nair wrote:
> +1
>
> On Thu, Mar 31, 2016 at 1:20 PM, Sergey Shelukhin
> wrote:
> > There have been a few bug fixes since 2.0, some more might be in the
> > pipeline.
> > I think it’s a good time to release 2.0.1.
> > I will go thru the log d
+1
On Thu, Mar 31, 2016 at 1:20 PM, Sergey Shelukhin
wrote:
> There have been a few bug fixes since 2.0, some more might be in the
> pipeline.
> I think it’s a good time to release 2.0.1.
> I will go thru the log diff between master and branch-2 and see if
> anything needs to be backported, peopl
There have been a few bug fixes since 2.0, some more might be in the
pipeline.
I think it’s a good time to release 2.0.1.
I will go thru the log diff between master and branch-2 and see if
anything needs to be backported, people can also mark JIRAs as
2.0.1-targeted.
Depending on how many of the la
