+1
On Feb 6, 2017 20:19, "Robert Metzger" wrote:
> Hi,
> according to our recent time-based releases discussion, I came up with the
> following deadlines for the upcoming 1.3 release:
>
> *Feature freeze (branch forking)*: 1 May 2017
> *Code freeze (first voting RC)*: 15 May 2017
> *Release da
Quick reminder:
*The feature freeze is 1 week from now (May 1)*
On Mon, Mar 6, 2017 at 1:03 PM, Stephan Ewen wrote:
> Looks good to me!
>
>
> On Mon, Mar 6, 2017 at 10:55 AM, Robert Metzger
> wrote:
>
> > That's the right attitude :)
> >
> > Since one month has passed since my initial email on
Looks good to me!
On Mon, Mar 6, 2017 at 10:55 AM, Robert Metzger wrote:
> That's the right attitude :)
>
> Since one month has passed since my initial email on the 1.3 release,
> here's a quick reminder for everybody that we have the following deadlines:
>
> *Feature freeze (branch forking)*:
That's the right attitude :)
Since one month has passed since my initial email on the 1.3 release,
here's a quick reminder for everybody that we have the following deadlines:
*Feature freeze (branch forking)*: 1 May 2017 (*8 weeks from now*)
*Code freeze (first voting RC)*: 15 May 2017
*Release
+1, we can do it this time! :-)
On Mon, 6 Feb 2017 at 20:19 Robert Metzger wrote:
> Hi,
> according to our recent time-based releases discussion, I came up with the
> following deadlines for the upcoming 1.3 release:
>
> *Feature freeze (branch forking)*: 1 May 2017
> *Code freeze (first voting
Hi,
according to our recent time-based releases discussion, I came up with the
following deadlines for the upcoming 1.3 release:
*Feature freeze (branch forking)*: 1 May 2017
*Code freeze (first voting RC)*: 15 May 2017
*Release date*: 26 May 2017
I will try to post into this thread monthly to
