[haiku-development] Re: Proposal from Begeistert: Getting Ready for the First Beta

  • From: Krishna <v.krishnakumar@xxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Tue, 17 Sep 2013 18:39:50 +0530

On Tue, Sep 17, 2013 at 2:57 PM, Stephan Aßmus <superstippi@xxxxxx> wrote:

> Am 17.09.2013 11:01, schrieb Marcus Jacob:
>> But all the above arguments are driven from a technical point of
>> view. Now let's try to look at it from a marketing point of view.[...]
>> Therefore I think its important to not only judge release or not and
>> when to release based on the given technical facts, but also from a
>> marketing point of view. And since the last release is almost a year
>> ago,  from a marketing point of view it makes sense to push a new
>> release for this fall.
>> This will create a slight buzz again and might keep Haiku on the
>> radar, even though all those mobile stuff seems to be much more
>> interesting at the moment.
> When and if PM is "usable" as the basis even for a rolling release, it is
> clear there has to be at least one more "regular" release that kicks it off
> and gets PM onto the hard drives.
> If people agree a release should be done, for whatever reason, the next
> question is always what should be in it, feature-wise and bug-fix-wise, in
> order not to give a bad impression with that release. A release most likely
> generates buzz. But an aweful, buggy release might not bode well with the
> audience we want to attract. Which would be a small percentage of those
> "give a short try once a new official release is out" types that happen to
> be developers and could be motivated to start contributing.
I think the OpenBSD's release process[1] could work well for Haiku as well.
OmniOS also follows a similar model[2]

[1] http://www.youtube.com/watch?v=i7pkyDUX5uM

[2] http://omnios.omniti.com/wiki.php/ReleaseCycle

Programming is difficult business.
It should never be undertaken in ignorance.
--Douglas Crockford, "Javascript: The Good Parts"

Other related posts: