I believe so. Chris, do you have things in particular to do before the release?
On 5/30/19 5:14 PM, John Thornton wrote:
Doesn't the whole release process of historically 5 to 8 pre-releases before the
actual release take several months to complete?
JT
On 5/30/2019 5:01 PM, Gene Heskett wrote:
On Thursday 30 May 2019 02:15:59 pm Chris Morley wrote:
Yes a couple weeks is way too short.
A couple months is more like it.
Chris M
I'm with Chris, see why below.
-------- 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
-------- 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.
Maybe, but its recorded. Which I consider an advantage.
I am relatively busy here, and while I'll update a couple times a week
since I can do that late at night, but its not that often I get a chance
to make chips and really test things recently. So as a tester, I'm
almost out of business. You're getting far more complaints from this
stretch install of your most recent "testing" iso, on the "I expect it
to do everything house machine" that is still 100 ft of cat5 and several
walls away from any of my "it cuts metal" machines. When I do get a
chance to play, I'll likely pester you folks for a sample configure
script so I can try to build master right on the pi thats running my
sheldon. That will be slow, but should go ok on a 120Gb SSD. Amazingly,
if I stay away from more than a j2 while building a kernel, the existing
small fan cooler seems to make it bulletproof, I'm now getting uptimes
from power bump to power bump.
JT
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
Cheers, Gene Heskett
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
--
And as it is appointed unto men once to die, but after this the judgment:
So Christ was once offered to bear the sins of many; and unto them that look
for him shall he appear the second time without sin unto salvation.
(Hebrews 9:27-28)
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
