[haiku-development] Re: Haiku releases going forward.
- From: Niels Sascha Reedijk <niels.reedijk@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sun, 30 Sep 2018 16:09:53 +0200
Hi Alexander,
Op za 29 sep. 2018 om 16:44 schreef Alexander von Gluck IV <
kallisti5@xxxxxxxxxxx>:
We *really* need to keep up with releases. I know the nightly images offer
all the things we need, but not having releases makes people think we're
stagnating.
With that said, too many releases also aren't appealing since they wear
on our small team (and make people care less).
Now that we have a process in place, I think we should try to do yearly
releases.
Doing them in the fall has a certain romance (our logo has a falling leaf,
etc) and gives
us a single date to fixate on.
Thoughts? We have a lot of data right now on what a workable timeline is
to churn
out a release... let's start planning on the next one (with dates)
I think we should have a discussion about what a release for Haiku should
be, and I do have thoughts about that. Before going into the *next* release
(which in my understanding means R1+), I am more interested about the
current R1 release. We are currently in beta, but what's the end goal here?
I am thinking especially about the following:
* What are currently the features/requirements holding us out?
* If we are merely stabilizing, then what is the definition of stable?
To circle back to your question: I do think we should try to start a
discussion on what the development goals and models of Haiku should be
going forward. The current ideology is too much focused about a 90's vision
of operating systems and the operating system market. I would like to
explore what it means for us that operating systems have adopted to a more
periodic rolling release model, that backwards compatibility has a relative
meaning in the age of apps and automatic updates, that there will not be a
mainstream Desktop OS but that instead we should focus on a niche, and that
we need to find a way to support the interests of our developers, coerce
them into cooperation when it comes to finishing and polishing features,
and reward them with the joys of a release.
I don't know how to facilitate and manage that discussion, but I am
guessing it starts by inviting contributors, ex-contributors and community
members about their vision and hopes for the future. That can be the start
for a series of discussions and proposals.
But first R1. And as I stated above, I don't see why we should wait until
the next fall to release that.
Regards,
N>
Other related posts:
