Re: A few thoughts about 2.1.4
On Monday 4 January 1999, at 23 h 49,
Adam Di Carlo <adam@onshore.com> wrote:
> > Now that 2.1.4 is installed in slink, I'll close some bugs related
> > to the keymap, if nobody objects, and I'll try to trim down the list
> > of bugs by closing incredibly old bugs which cannot be solved now
> > anyway. No problem?
>
> Please go ahead.
Keytable-bugs 30826 30918 31235 31280 closed.
I'm attacking the bugs older than two years now. Nobody will regret their
historical interest?
> > So, what prevents slink from being released now?
...
> Boot disks for other architectures, and all the bugs still in that...
>
> Documentation! I need much more agressive patching from people
> running other platforms.
My concern is that slink is frozen for a very long time. People on
debian-devel are even asking that we drop it and start with potato! I'm not in
favor of it, since this would mean to start again so many tasks but I just
want to be sure that the blocking factors are properly identified so people
who are ready to help can choose the right task.
It seems that all the problems are with non-i386 architectures? Is it OK to
regard them as experimental and to say that they should not stop the release
of the most used architecture? After all, you cannot invent the parts who
miss. If the people who work on other platforms have no time to update the
documentation, it shouldn't delay slink in its whole.
[Working on debian-cd and boot-floppies' install.sgml now.]
--
http://www.debian.org/~bortz/
Reply to: