Hi Guilers!
I agree with your suggestions.
I think ‘stable-2.0’ should only get changes that preserve the C ABI and
Scheme interface.
Additions of new public functions/procedures or modules are generally
welcome though they should discussed on a case-by-case basis IMO.
Thanks,
Ludo’.
Hey Mark,
On Sat 19 Feb 2011 19:25, Mark H Weaver writes:
> Andy Wingo writes:
>> can you ask to be added to the Guile group on Savannah? That will
>> allow you to commit directly. I would like for you to continue to
>> mail your patches to the list before pushing, just to make sure we're
>>
Hi Andy,
Andy Wingo writes:
> [...] What I meant was that we should aim for a 2.2.0 release within a
> year ot two; and that in the meantime we should focus on consolidating
> our gains with the 2.0 series. We need to get 2.0 into the distros,
> to see wider use of 2.0, and that will take a litt
Hi Mark,
On Sat 19 Feb 2011 00:54, Mark H Weaver writes:
> Andy Wingo writes:
>> Compatible changes on 2.0.x seem fine to me; we should live in 2.0.x
>> for a year or two I think.
>
> What do you mean by "live in 2.0.x"? Does this mean that we should
> avoid working on deeper changes to Guile
Andy Wingo writes:
> Compatible changes on 2.0.x seem fine to me; we should live in 2.0.x
> for a year or two I think.
What do you mean by "live in 2.0.x"? Does this mean that we should
avoid working on deeper changes to Guile for the next year or two?
What does this mean for my pending patches
Andy Wingo writes:
> On Fri 18 Feb 2011 21:37, Neil Jerram writes:
>
>> Now that 2.0.0 is out, I presume the general procedure from now on
>> should be:
>>
>> - committing safe 2.0.x stuff (in particular, as far as I'm concerned,
>> docs) to the stable-2.0 branch
>>
>> - committing anything el
On Fri 18 Feb 2011 21:37, Neil Jerram writes:
> Now that 2.0.0 is out, I presume the general procedure from now on
> should be:
>
> - committing safe 2.0.x stuff (in particular, as far as I'm concerned,
> docs) to the stable-2.0 branch
>
> - committing anything else to master
>
> - periodically
l...@gnu.org (Ludovic Courtès) writes:
> Hello!
>
> There’s now a ‘stable-2.0’ branch!
>
> We’re releasing in less than 24 hours so normally nothing will be pushed
> there. :-)
Now that 2.0.0 is out, I presume the general procedure from now on
should be:
- committing safe 2.0.x stuff (in partic
Hello!
There’s now a ‘stable-2.0’ branch!
We’re releasing in less than 24 hours so normally nothing will be pushed
there. :-)
There’s an additional jobset on Hydra for this branch:
http://hydra.nixos.org/jobset/gnu/guile-2-0
Normally you should soon be able to grab a tarball from there and
