[haiku-development] Re: R1/A3: a thought about the release cycle.

  • From: Jérôme Duval <korli@xxxxxxxxxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Tue, 9 Nov 2010 11:39:06 +0100

2010/11/2 Ingo Weinhold <ingo_weinhold@xxxxxx>:
> In theory yes, in practice this might turn out to be more complicated. E.g.
> there are at least a few components (ShowImage, ext2, the Gutenprint stuff,
> Locale Kit/ReadOnlyBootPrompt) for which I couldn't say what state they are
> in ATM. If any of those still requires significant work to get them into an
> acceptable state for the release, we would already have exceptions to the
> policy.

I believe there are only improvements in the case of ext2 (bugfixes +
features). I did quite many tests to ensure a decent quality for this
file system addon as IMO file systems need a higher standard of
quality than other OS parts. What's missing featurewise is writing
attributes support. There are probably still bugs in corner cases
(orphan management for instance). But file system consistency should
be at low risk, the volume goes readonly when the block allocator
failed to init correctly. The volume is now correctly synched on
shutdown.

About alpha state, annoying bugs I met are with ShowImage, ffmpeg
plugin and print_server crashing on shutdown (for this bug I might
need to update the buildtools with latest Ingo's changes).

Bye,
Jérôme

Other related posts: