Niels Reedijk wrote:
I don't have commit access, so I don't count as a developer. However, if input from such as myself has any weight:
There are roughly two options: a time based release and a feature based release. In the first case we will agree on a schedule and let time decide what goes in the next release. In that way, the next release will most likely be alpha 2. In the case of a feature based release, we will work on a feature list and release when those are satisfactory implemented. In this case the code determines when to release. This could potentially be beta 1 (if all the features for R1 are implemented).
Although I have played with the code and built Haiku myself (and even once submitted a very minor patch, although it was RDF-related, not code-related), I am really more of an end-user. As such, I would personally prefer to see new features sooner, rather than waiting until all the features desired for beta were ready.
Of course, I could always build it myself again if the developers do decide go the beta 1 route instead of the alpha 2 route. But I think a time-based release would also do more to keep Haiku in the news.
I know my vote doesn't count. Just letting you know what an end-user (at least this particular end-user) prefers, for whatever it's worth.