[haiku-development] Re: Request for vote for next release naming
- From: John Scipione <jscipione@xxxxxxxxx>
- To: "haiku-development@xxxxxxxxxxxxx" <haiku-development@xxxxxxxxxxxxx>
- Date: Mon, 10 Feb 2014 18:36:16 -0500
On Mon, Feb 10, 2014 at 5:46 PM, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:
> On 02/10/2014 11:20 PM, John Scipione wrote:
>> On Mon, Feb 10, 2014 at 5:16 AM, Ingo Weinhold <ingo_weinhold@xxxxxx>
>> wrote:
>>>
>>> As for when we start beta releases, I think we should make a detailed (!)
>>> list of features that we want in R1 and do the first beta release when
>>> all of them have been ticked off (or removed).
>>
>> We already have a detailed list:
>> https://dev.haiku-os.org/wiki/FutureHaikuFeatures
>>
>> The question is, has each item has been checked off? If yes, beta1, if
>> no, alpha5
>
> 1. The list from the poll results is three years old and may need to be
> revised. E.g. what about IMAP?
The poll results being 3 years old doesn't really matter because R1
shouldn't be a moving target, the features required for release 3
years ago should be the same as today.
Whether a feature is done or not is an open question, who decides if a
feature is done? I don't know. A good rule of thumb IMHO is that a
feature is done when it works for most people. So, in the case of
email, I'd say that it only works for most people with IMAP support.
Email isn't listed as an R1 pre-req on that page though so *shrug*.
> 2. When I write detailed, I mean detailed. E.g. there are two PM related
> propositions -- #30 Upgrade Management and #31 (general) Package Management
> -- but there are plenty of PM subtasks (package metadata localization,
> HaikuDepot web app, plenty of HaikuPorts/HaikuPorter tasks, general
> infrastructure,...) which IMO warrant individual listing and inclusion
> decisions.
The detailed list of items and subitems needed for release is the bug
tracker. If something is missing a ticket should be filed in the bug
tracker for it, and if it's a release blocker it should be marked as a
blocker. Maybe you'd like something better than that, but, that's what
we've got right now.
Would it be worth it to compile the list of tickets into a detailed
feature list, and then vote on each item, adding missing tickets were
needed? That's a lot of work, but necessary if we want to nail down
the precise definition of beta in an impartial way. I'm sure my beta
list is different from your beta list is different than other's beta
list.
> 3. While the pie charts are nice and all, a compact list representation
> (including subitems where necessary) would be a lot more helpful. Also,
> those are the user poll results. IIRC the contributor poll results didn't
> agree on all accounts.
I recall there being contributor poll results in that survey too.
Maybe someone can point to them. I don't recall them being
contradictory to the user poll results in most cases, perhaps just for
mode-setting video drivers, and that's a moot point because we now
have mode-setting drivers for Intel and Radeon HD.
Other related posts:
