[haiku-development] Re: Pre-proposal: Roadmap to Haiku R1 Release
- From: Panagiotis Vasilopoulos <hello@xxxxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Mon, 14 Sep 2020 08:20:57 +0300
On 9/13/20 8:16 PM, Adrien Destugues wrote:
but even if doing that, we still have only limited man/hours
available, so maybe we should make it a bit longer (would 1 month
between each make sense?), especially with christmas happening in the
middle of the final crunch (in my case at least, that means less time
spent in front of a computer).
Agreed. I'd also like some more time between releases and perhaps
increasing the amount of beta releases in order to increase overall
productivity over the course of the year, in order to be able to listen
and react to feedback accordingly. I feel like a small amount between
releases right now may make what needs to be done next even less clear,
due to excessive amounts of regurgitated feedback, and that this project
would not be able to keep up with a potential influx of users and/or
potentially new contributors.
Although it's true that many people closer to the project may be able to
work under the current circumstances regarding the pandemic, the
increased amount of sociopolitical instabilities that can directly
affect other contributors' lives and their actual ability to function
not only within the project itself, but in general, may mean that
certain details that aren't normally managed by the core developers
(e.g. internationalization, some apps that are mostly managed by
specific people) may not be at an optimal stage before the final deadline.
I think that striving to release something with the label "stable" could
backfire, and I'm not sure whether publications or hobbyist YouTube
creators/bloggers would be interested in reprinting effectively the same
stories over the course of a quarter, let alone a month or two weeks.
Shipping something is important, but just pushing something out there
while community members/users have trusted the "we'll release it when
it's done" mantra over the past 2 decades could pose a risk of betraying
that established trust, if the issues are actually way more than
expected and practically unmanageable by the team. Other factors that
normally play a role in spreading information across the internet (e.g.
SEO, or services like Google News) could also operate in a manner that's
counterproductive as far as receiving feedback and maximizing the
interest revolving around the project are concerned.
I'd also like to suggest avoiding GUI-related changes that do not
involve bugs right before the final release, because those changes may
pose the need to modify existing strings, which could pose a burden to
the people working on i18n. It would also be worth improving the
documentation, in order to manifest the current increased amounts of
interest revolving around Haiku productively, while taking some of the
mentoring work off the shoulders of the developers. I'll try to look
into the latter.
Regards,
Panos
Other related posts:
