LC8 release structure

2017-11-28 Thread Alejandro Tejada via use-livecode
Does exists some way to install only the files changed between each version and keep all common files available for each LC version in use? In this way, instead of using 1 Gb for each new Livecode version installed, we could keep a folder with common files and each new LiveCode version would occup

Re: LC8 release structure

2017-11-28 Thread Monte Goulding via use-livecode
> On 29 Nov 2017, at 1:06 pm, Mark Wieder via use-livecode > wrote: > > Well, yes, I got that from the release notes. > > But I see that one of my bug reports (#9505) is now resolved as being fixed > in LC8.2-dp2. So is it that the 8.2 development channel is getting bug fixes > a month ahead

Re: LC8 release structure

2017-11-28 Thread Mark Wieder via use-livecode
On 11/28/2017 04:32 PM, Monte Goulding via use-livecode wrote: The 8.2 release cycle is mainly for IDE features like autocomplete that could potentially be disruptive and need a bit of iteration. Well, yes, I got that from the release notes. But I see that one of my bug reports (#9505) is now

Re: LC8 release structure

2017-11-28 Thread Monte Goulding via use-livecode
The 8.2 release cycle is mainly for IDE features like autocomplete that could potentially be disruptive and need a bit of iteration. > On 29 Nov 2017, at 10:15 am, Mark Wieder via use-livecode > wrote: > > I'm confused now by the number of unstable releases in flight. > > I'm seeing > LC8.2.0

LC8 release structure

2017-11-28 Thread Mark Wieder via use-livecode
I'm confused now by the number of unstable releases in flight. I'm seeing LC8.2.0-dp2 dated 11 October 2017 LC8.1.8-rc2 dated 23 November 2017 and of course LC9.0.0-dp10 dated 23 October 2017 I'm fine with the slow progress on LC9, although I keep waiting for the CEF business to be fixed, but I