[haiku-development] Re: Task list for alpha 1
- From: Christopher Dobbs <crdobbs@xxxxxxxxxxxxx>
- To: "haiku-development@xxxxxxxxxxxxx" <haiku-development@xxxxxxxxxxxxx>
- Date: Fri, 21 Aug 2009 11:14:04 -0400
My company, LybreDyne Technologies, would be honored to become a mirror for
Haiku.
We would like to offer storage on one of our Linux servers, named Ishiyama.
If this is acceptable, would the requisite persons please email me back.
Christopher Dobbs
Software Developer
LybreDyne Technologies
(503) 914-0799 x2213
http://www.lybredyne.net/
NOTICE: The information contained in this e-mail is confidential and may be
privileged or otherwise protected from disclosure. This e-mail is intended
solely for the use of the named addressee. Please be aware that any other use,
printing, copying, disclosure or dissemination may be subject to legal
restriction. If you are not the intended recipient, please notify us
immediately by return e-mail to the sender and delete from your computer.
Although we attempt to sweep e-mail attachments for viruses, it does not
guarantee that either are virus-free and accepts no liability for any damage
sustained as a result of viruses.
-----Original Message-----
From: haiku-development-bounce@xxxxxxxxxxxxx
[mailto:haiku-development-bounce@xxxxxxxxxxxxx] On Behalf Of Niels Reedijk
Sent: Friday, August 21, 2009 06:10
To: haiku-development@xxxxxxxxxxxxx
Subject: [haiku-development] Task list for alpha 1
Hi gang,
I took some time to build a list of tasks that we need to release
alpha 1. See the wiki for the complete list of tasks, with their
respective task owners.
http://dev.haiku-os.org/wiki/R1/AlphaStatus
There are a few tasks unassigned. There might be some unclear (as they
are in my head mainly). Some unassigned tasks are for non-devs as
well. Others have been started, but no one is officially responsible
yet.
Please review the task list and comment if you have anything to add or
if you want to take one of the tasks.
Kind regards,
N.
Attachment:
1. BUILD TASKS
a) assign buildmeister (Matt?)
b) determine distribution structure (haiku-files.org)
c) Determine optional packages to be included
d) Set up a test framework (what tests need to be passed in order to
qualify a build as 'good'?)
2. RELEASE PREP
a) find mirrors
b) Write release notes (all known issues)
c) Write press release
d) Determine press plan (in other words, do we go big on this one or
will we keep it small)
3. WEBSITE
a) finish new theme (Koki)
b) migrate to D6 (Daniel + Niels)
c) Make the documentation available
d) Prepare a good starting point for those interested in the release.
4. RELEASE
a) branch the source tree (Axel)
b) backport important bug fixes
c) tag the final build + make source available
Other related posts:
