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
-------- Original message --------
From: Moses McKnight <mo...@mcktex.com>
Date: 2019-05-30 8:40 a.m. (GMT-07:00)
To: EMC developers <emc-developers@lists.sourceforge.net>
Subject: Re: [Emc-developers] 2.8 Release planning
There is a release checklist here:
http://wiki.linuxcnc.org/cgi-bin/wiki.pl?ReleaseCheckList
Some of the work involves the buildmaster, so I think either Seb will have to do
some of that or give someone else access to do it.
The live image does need to be made as well.
Another thing that will require some work is documenting all the changes from
2.7 to 2.8
You may be right about mailing list over IRC. Taking a few days to discuss
something is probably not bad though.
Moses
On 5/30/19 8:26 AM, John Thornton wrote:
Yep lets do it!
What else has to be done to get the release out after creating the branch?
I assume we need to have a 2.8 LiveDVD at some point?
I think timing is an issue for IRC meetings, one advantage to the mailing list
is you don't have to be there at any specific time. The disadvantage is it can
take a few days to discuss something on the mailing list.
JT
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
