On Thu 28 May 2009 23:27, l...@gnu.org (Ludovic Courtès) writes:
> There's one more item:
>
> licensing:
> Switch to LGPLv3+, as was decided some time ago. Check the license
> headers of new code and code inherited from Guile-VM.
Good point. I switched over the headers for VM .c code t
Hi,
Andy Wingo writes:
> Here are the features that I know of, in no particular order:
>
> BDW-GC:
>Looks really promising. All the code is there. Unknown implications,
>needs lots more testing. Needs to see at least one and hopefully two
>micro releases. (1.9.x)
>
> R6RS library s
Andy Wingo writes:
> To be honest, I'd rather not [have to] handle release mechanics -- while
> I can do it, I would be more than happy for you to keep handling
> releases, Ludovic.
Fine with me. I'll do my best to be available on the 14th-15th of each
month, then.
> Or perhaps we should share
Hi!
Andy Wingo writes:
> Yes. We probably would need the longer freeze (of 10 days) to get the
> docs and NEWS and things in shape for this one, meaning no new code
> should go in between the 5th and the 15th, just testing and doc updates
> and regression fixes. Sound good to you?
Yes, but...
On Thu 28 May 2009 00:15, Neil Jerram writes:
> Andy Wingo writes:
>> (I tried distcheck today at work, and it worked fine.)
>
> That's curious. It's failing at the moment for me (as I mentioned in
> another email). I guess my action to look into that failure then.
Hm, is failing for me here
Hello!
On Thu 28 May 2009 15:01, l...@gnu.org (Ludovic Courtès) writes:
> For 2.0, though, I think it may be wiser to let Andy take care of it, if
> he wants to: he's been more responsive than me, and he's the 2.x guy
> after all. ;-) Andy: what do you think?
>
> (I'm happy to take care of it i
On Wed 27 May 2009 01:48, l...@gnu.org (Ludovic Courtès) writes:
> This all sounds like an excellent plan to me!
Excellent!
I love it when a plan comes together!
> In practice, that would mean making the first release on June 15th,
> right?
Yes. We probably would need the longer freeze (of 10
Hello!
Neil Jerram writes:
> As regards the mechanics of releasing: recently Ludovic has handled
> that. Will you be OK to continue doing the releases to Andy's
> proposed schedule, Ludo; or Andy are you proposing to handle the
> release process yourself instead?
FWIW, I'm happy to keep releas
Andy Wingo writes:
> (I tried distcheck today at work, and it worked fine.)
That's curious. It's failing at the moment for me (as I mentioned in
another email). I guess my action to look into that failure then.
Neil
Andy Wingo writes:
> My proposal would be a time-based release schedule. We can decide the
> Guile 2.0 release date now, and three or four micro releases before
> then.
>
> August in Europe is rather slow, and September people are catching up,
> so I would propose October 15 for Guile 2.0. Then
Hello Andy!
This all sounds like an excellent plan to me!
In practice, that would mean making the first release on June 15th,
right?
Ludo'.
> Hey folks!
>
> So, IMO we need to start pushing towards a release. How about getting a
> 1.9.1 out soon?
>
> Unicode:
>Code shaping up, needs review and R6RS-libs. Unclear how much will be
>in shape for 2.0. Acceptable to ship with only the finished parts.
>
The big steps to hit a be
Hi Andy,
> R6RS library support:
> No code yet. Julian? :-)
Yeah... As I mentioned on IRC, I punted temporarily on that while I
was rewriting the parser for my CSS library. Just yesterday, though,
I started doing some initial work towards adding version information
to modules and the module-
Hey folks!
So, IMO we need to start pushing towards a release. How about getting a
1.9.1 out soon?
My feeling is that the current feature set in master is ready for a
release. We could just distcheck and that's that. (I tried distcheck
today at work, and it worked fine.)
But there are a few feat
14 matches
Mail list logo
