This is the mail archive of the guile@cygnus.com mailing list for the guile project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

What now?


Jim Blandy writes:
 > 
 > I have bug reports that still aren't dealt with in the 1.3 release,
 > but I wanted to get 1.3 out there, so projects like SCWM and GNOME can
 > refer people to something released that doesn't have a hopelessly
 > out-of-date API.

That's the best solution.

 > 
 > The snapshots are now calling themselves 1.3.1.  I'm planning to do a
 > bug-fix release, 1.3.2, in about a month.  I want that one to clear
 > all known bugs (for some reasonable distinction between "bug" and
 > "misfeature" :) ).
 > 
 > I think you won't hear from me much for the next few days, because my
 > real job is probably getting kind of annoyed at this point... :)
 > 
 > As I've said before, I don't intend to do much development for the
 > next few months; I think the lack of documentation is Guile's most
 > serious problem, so I'm mostly going to concentrate on pulling the
 > manual together, and fixing bugs.

The doc thing is absolutely necessary. Maybe then I won't have to ask too many
stupid questions on here, which should be answered by a simple search in an 
info buffer. The distribution of data-rep with the core dist was one of the
greatest moves. Would have saved me months if it had been this way a year ago.

 > 
 > Aside from that, there are a bunch of patches I've put off, people
 > have code they want me to look at, and there are cool things other
 > people have worked on --- for example, NIIBE Yutaka has some changes
 > to give Guile real thread support that look good, and Maciej said
 > something about maintaining a package archive --- so I want to pick
 > those conversations up again.

So the best time to send Jim B. stuff like the wannabe- curses-module would be
in a few days? 
 
 > 
 > If there are other things you want Guile to do, the best thing you can
 > do is to just start hacking on them, and post your code!  I love it
 > when that happens.  :)

Even if it's code of over 10kB ? 

 > 
 > Anyway, thanks again for all your bug reports, patches, and ideas.
 > 

I only reported misunderstood features, sorry.

       Klaus Schilling