On Nov 6 2017, Kon Lovett wrote:
CHICKEN 4 LTS
create a "Foundation for the Continuation" to support all NEKCIHCs
...for a to-be-defined length of "long term"; sign me up.
Porting hundreds of modules and thousands LOC may or may not reveals
issues. Once that's done only, we can see how we'd
CHICKEN 4 LTS
create a "Foundation for the Continuation” to support all NEKCIHCs
> On Nov 5, 2017, at 3:09 PM, Evan Hanson wrote:
>
> Hi all,
>
> I think we should:
>
> 0.) Fix 1399 in master and chicken-5.
> 1.) Tag 4.13.0rc1.
> 1.1, ...) Iterate until we have a good RC, release as 4.13.0.
>
Hi all,
I think we should:
0.) Fix 1399 in master and chicken-5.
1.) Tag 4.13.0rc1.
1.1, ...) Iterate until we have a good RC, release as 4.13.0.
2.) Rename master to chicken-4.
3.) Rename chicken-5 to master.
From that point on we develop on master while chicken-4 gets security
patches only. W
* John Cowan [171028 22:15]:
> On Sat, Oct 28, 2017 at 2:27 PM, Peter Bex wrote:
>
> Also, what happens to the CHICKEN 4 line after 5.0 is out?
> >
>
> 1) Pick a EOL date for Chicken 4.
>
> 2) Stop accepting patches except security patches.
>
> 3) Accept security patches until the EOL date.
>
On Sat, Oct 28, 2017 at 2:27 PM, Peter Bex wrote:
Also, what happens to the CHICKEN 4 line after 5.0 is out?
>
1) Pick a EOL date for Chicken 4.
2) Stop accepting patches except security patches.
3) Accept security patches until the EOL date.
4) Profit!!!
--
John Cowan http://vrici
Hi all,
I'm a bit confused what should be the best course of action regarding
CHICKEN 4. Should we start the release process for 4.13, or should we
merely make a 4.12.1 development snapshot?
What are we going to do with #1399?
Also, what happens to the CHICKEN 4 line after 5.0 is out?
Cheers,
