Hi, On Fri, Mar 14, 2008 at 03:58:33PM +0100, Arne Babenhauserheide wrote: > El Friday, 14 de March de 2008 15:08:31 Carl Fredrik Hammar escribió:
> > Most of the recent changes has been on the L4 branch, which was > > originally an attempt to port Hurd to the L4 micro kernel. That > > didn't work out for various reasons, so currently they are > > experimenting with their own kernel until something better comes > > along. (Disclaimer: I'm not a 100% sure on any of this.) > > Does that already run? Would it be possible to turn it into a livecd > or qemu image? It does run, but does nothing that would be interesting to a user. Currently it's only a proof-of-concept implementation of Neal's research work; it's not interesting for anything else than this research (yet). > If you find a list, that list should go into the wiki, along with a > roadmap on which things can be marked "done". > > That means, the Hurd needs something like the Shedules in KDE: -> > http://techbase.kde.org/index.php?title=Schedules > > Each new release just needs a todo list with bugs and features. I totally agree that some kind of roadmap would be useful in general. (Problem is that everyone has different priorities. Any roadmap would reflect a particular person's goals; I doubt we could come up with one generally agreed on...) However, I think that conditioning releases on any particular milestones is a bad idea in general. Whenever the current state has visible improvements over the last release (and doesn't introduce too many new problems), it's worth a new release. That doesn't really need any planning in advance... -antrik-
