I agree. I suggested the end of June in my reply to Andy, so how about setting
the date for RC1 at July 1.
If fixes are still coming in fast then that could be extended, but does that
sound like a reasonable goal for RC1?
Moses
On 5/30/19 2:43 PM, mydani wrote:
Maybe select a date which is not to far in future and see what's really
coming in.
If it's only few things, go for RC1 early, and use RC2 / 3 /...
If nothing's coming in anymore in terms of bugs, release might not be to
far away.
Daniel
Am Do., 30. Mai 2019 um 20:16 Uhr schrieb Chris Morley <
chrisinnana...@hotmail.com>:
Yes a couple weeks is way too short.
A couple months is more like it.
Chris M
-------- Original message --------
From: Moses McKnight <mo...@mcktex.com>
Date: 2019-05-30 9:48 a.m. (GMT-07:00)
To: emc-developers@lists.sourceforge.net
Subject: Re: [Emc-developers] 2.8 Release planning
I'm thinking we should give a couple of weeks (depending of course on if
we can
get the work done) to get the initial stuff done and then make an rc1
release
candidate. Then wait a couple of weeks or so to see if anything critical
turns
up. If not, release, if so, go through and rc2 and etc.
Do you have any other ideas?
On 5/30/19 10:20 AM, Chris Morley wrote:
How long are we giving for bug fixes docs and stabilizing. Roughly?
Chris M
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
