[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Sun, 10 Feb 2002 20:28:11 -0800
I've just committed a bare-minimum patch to get inetutils running
under autoconf 2.52. I have also tested that srcdir!=builddir builds
work correctly, and we also now (finally!) pass a make distcheck.
I realised that if I hold the release up until I get all the work I
want to do on the build system done, it won't happen before I'm back
from my wedding.
Alain, I'd like to take control of the next few releases with the
following targets in mind:
This is the 1.4.0 release, to celebrate the fact that it should
compile and that we have a new ping, gwhois, and talk. I would like
to release this by the 21st of February.
The 1.4.1 will be a maintenance release with various patches
discovered from 1.4.0 and the build system reworked. I probably won't
start work on this until I'm back at the end of March. Assume a
summer release or so.
1.5.0 will be a release that tries to put as much as possible into
libraries (startup code, etc). I also would like to try and write (or
convince someone else to write) a gopher and gopherd pair.
This whole process will take probably until the end of the year to get
there, so I don't think there's any point in predicting what happens
after that, although I have a silly dream of getting all the non-FSF
copywritten code out of inetutils for a 2.0 release... =)
I want to go live with the guy who came up with the phrase "Free like
- Patch committed,
Jeff Bailey <=