Context Navigation

Alpha 1 Proposals

Voting is now open.

This page is closed for editing (and marked read-only). Administrators can edit this page, but are kindly requested to not edit this page while voting is in progress, because this might cause the polls to forget some votes. Thank you!

This page lists concrete proposals that came out of a discussion.

All developers, plus people who offered to adopt a task now can vote.

About what you are voting for:

This vote is about requirements for alpha 1. This means that voting in favor for something means that you want this feature to be absolutely for sure in the alpha. So for example, if you vote in favor for # 9 (fully integrate IO scheduler), you actually say that you want the release blocked until this feature is finished.

In this same vain, voting against making a proposal mandatory for release, does not mean that in the end this feature will not end up in the release. For example, if the I/O scheduler does not get enough votes to become necessary, but it is finished in time, it might as well end up in the package. Of course, this does not work for bundled software vote.

About the voting:

The voting is not anonymous. Your vote will be registered, and anyone who is logged into Trac, can see your vote.

Voting starts at Sunday the 14th of September and it will end Monday the 22nd of September at 10:00 (AM) GMT.

During the period, you may alter your vote.

Because of technical limitations, you have to click the vote button for every vote you make. You cannot fill out the whole page and then click on one vote-button, you will lose your data.

After the poll closes, the votes will be counted, and published.

A proposal is accepted with a majority vote. When there is a draw, the proposal will go to the mailing list for discussion, and there will be decided what will happen.

General Proposals

The proposals are general when they apply to procedures, requirements that cannot be quantified or qualified, or tendencies that are not covered by sections deeper down.

Prop # 1: All known bugs that cause data corruption need to be resolved before the release

Speaking in general terms, the important thing, even for an alpha, is
that we have no know bug that can cause data corruption. As long as
we reach a point where we are reasonably certain that this is the case,
everything else can be attributed to it being an alpha. :)

Accept Proposition # 1?

Yes

No

You don't have permission to vote. You may need to login.

Prop # 2: Name the release 'Developer Release 1'

Adopted by: no one

No vote since it is a non-development related issue

Prop # 3: Create a welcome package

Adopted by: no one

Have links on the desktop that refer first time experimenters to things that they can do next.

Have a short 'what to do next'-guide

Accept Proposition # 3?

Yes

No

You don't have permission to vote. You may need to login.

Prop # 4: Release as the GCC 2/4 hybrid

Adopted by: no one

The release should be done in such a way that applications compiled with GCC 2 and 4 can run out of the box.

Prop # 5: Make sure that a live Haiku install can be updated

The release coordinator will be a community volunteer that investigates the required work to prepare for a release, and report this info back to the developers and Haiku Inc.

Areas of investigation should be marketing, bandwith and mirrors, procedures to streamline the release.

The volunteer does not have to be a developer. Community members are encouraged to join in the process.

The volunteer is selected per developer vote.

Accept Proposition # 6?

Yes

No

You don't have permission to vote. You may need to login.

Prop # 7: Set a preliminary freeze date for alpha 1

Adopted by: nielx

Set a date on which the source repository is freezed and where alpha 1 will be finished.

Accept Proposition # 7?

Yes

No

You don't have permission to vote. You may need to login.

Prop # 8: Finish and Include Swap File Support

Adopted by: bonefish

Swap file support is GSoC project. It should be got into a reasonably working state and enabled by default. Without swap file support machines with less than about 800 MB RAM won't be able to build Haiku.

Accept Proposition # 8?

Yes

No

You don't have permission to vote. You may need to login.

Prop # 9: Fully Integrate I/O Scheduler

Adopted by: bonefish

As reported the CD boot is extremely slow. Finishing and fully integrating the I/O scheduler should improve this situation significantly.

Accept Proposition # 9?

Yes

No

You don't have permission to vote. You may need to login.

Prop # 10: Read-ahead feature

Adopted by: no one

Accept Proposition # 10?

Yes

No

You don't have permission to vote. You may need to login.

Prop # 11: Recruit release manager

Adopted by: no one

The release manager should be responsible for the creation and maintenance of the R1/Alpha1 branch. That might also mean identifying changesets against trunk that should be applied or even ported to the branch once it is set up.

This person differs from proposition # 6, as in that this manager is a developer maintaining the actual code part of the release, and the release coordinator performs the marketing, mirrors and other logistics behind the release.

Accept Proposition # 11?

Yes

No

You don't have permission to vote. You may need to login.

Prop # 12: ATA vs. IDE bus manager

Adopted by: no one

There are still some pending issues with our "ide" bus manager. The "ata" bus manager seems to work better, but a) takes a long time to boot, and b) does not yet implement DMA. We should either fix "ide", or complete "ata" for the alpha.

Software proposals

Prop # 20: Include the Development tools

The development tools currently in the 'Development' package should be included. Currently that means: (​Rene Gollent)

gcc 2.95.3

autoconf-2.61

automake-1.10.1

bison-2.3

flex-2.5.35

jam

libtool-1.5.26

texinfo-4.11

Perl 5.10

Accept Proposition # 20?

Yes

No

You don't have permission to vote. You may need to login.

Prop # 21: Include Firefox

Adopted by: nielx

Include the latest version of Firefox. nielx: "I have built Firefox before, and I have even submitted one or two patches to it, so I will take care of having a good binary that can be distributed with the alpha."