I have been clearing the testsuite. Other guys are working with me on
that (Francesco, Justin for instance). I'll do as soon as I'm done.
On Thu, May 10, 2018 at 8:24 AM, Christopher Shannon
+1 to make this a 2.6.0 release, there are now over 80 commits and
been enough time that I think a 2.6.0 makes more sense
On Thu, May 3, 2018 at 12:09 PM, Clebert Suconic
Meanwhile please set your fixes as 2.5.1... i will rename it as 2.6.0
before releasing as everything is already filtered there.
On Thu, May 3, 2018 at 12:04 PM, Clebert Suconic
From the entire set.. we only have fixes.. and 4 enhancements...
(previously existent features).
I would prefer saving 2.6.0 for a more substantial release.. but if
you guys still prefer calling 2.6.0 I'm fine with that.
On Thu, May 3, 2018 at 11:02 AM, Robbie Gemmell
I see there are some updates retargetting JIRA version at 2.5.1 from
2.6.0. I think the changes on master are now more suited to the
release being versioned as 2.6.0. There are plenty of changes in the
time since 2.5.0 that would have suited 2.5.x releases, but there
seems to be enough others in there now that might better fit a 2.6.0
due to adding new functionality etc.
On 26 April 2018 at 22:46, Clebert Suconic <clebert.suconic@xxxxxxxxx> wrote:
Little snafu today... I'm dealing with a failure in
will send the vote soon.
On Wed, Apr 25, 2018 at 9:24 PM, Clebert Suconic
I will cut it tomorrow. I won’t merge anything until it’s out.
@Commiters please don’t break Anything today :)
@everyvody if there is anything you want Merged or committed tomorrow let me
On Wed, Apr 25, 2018 at 4:41 PM pwjenkins
Are you on track to release by the end of April?