[haiku-development] Re: Task list for alpha 1
- From: Niels Reedijk <niels.reedijk@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Mon, 7 Sep 2009 09:01:46 +0200
Hey!
Sorry, acute illness left me missing in action past weekend.
2009/9/6 Jorge G. Mare <koki@xxxxxxxxxxxxx>:
> Howdy,
>
> Niels Reedijk wrote:
>> b) Write release notes (all known issues)
>>
>
> Is anyone working on the release notes?
>
>> c) Write press release
>>
>
> Niels, are you really going to work on this? Being my area of expertise,
> I would be glad to take over if you are time-constrained.
I have done some reading on other release notes and I took some notes,
but did not get to the actual writing. I think I am feeling too fuzzy
to finish this now, so I would be glad if you would give it a go.
Replying to Ryan somewhere in this thread: I would rather not throw
the draft press release into the world, but rather share it privately
between a few people who have interest in reading it, in order to
avoid that any 'news' outlet picks it up. I was planning on sharing a
google doc, but feel free to pick another format.
>> 3. WEBSITE
>> a) finish new theme (Koki)
>>
>
> This is almost done. You can take a peek at the following test site:
>
> http://test.haikuzone.net
>
>> b) migrate to D6 (Daniel + Niels)
>>
>
> This seems to be stalled; at least, I am not seeing anyone working on it
> nor am I getting any response to the query that I sent to the haiku-web
> list a few days.
Also one that I put on the weekend-list of emails to respond to, but
it got stalled. I will be here to help you out with that one.
> I really don't want to have to work on the website upgrade at the
> eleventh hour without any planning (which is the status quo). So unless
> anybody opposed, I would like to take over this task right away.
>
> To make the upgrade smooth, I propose a 7 day transition period that
> starts with making the live site read-only and that ends on 9/14 when
> the upgraded site goes live. This is what would happen in that
> transition period:
>
> 1) Live site (now on Drupal 5) is made read-only, with a notice to that
> effect being displayed on all pages.
How will we do this though? Is there an actual way to make it
read-only? Or do we tweak permissions so that people can't post
comments and forum posts anymore?
> 2) Start Drupal 5 to Drupal 6 migration on test installation site (where
> all the the steps that follow take place).
>
> a. Migrate D5 database to test site.
>
> b. Update all modules.
>
> c. Enable new website theme.
>
> d. Migrate content types (this is desired in order to get rid of a
> buggy/resource intensive non-core module).
>
> e. Migrate all Drupal views (queries that are used to generate various
> Gmap/date-based pages, etc.)
>
> f. Add the new Screenshot Tour and submit for peer review.
>
> g. Adjust content of pages such as About, FAQ, etc. to reflect the
> release of Alpha 1. Submit changes for peer review as they are made.
>
> h. Add mirrors to new Downloads page (will work on this with Urias).
>
> During the transition period, bug reports can be filed against the test
> installation so that we try to get all rough edges ironed out by the
> alpha 1 release date.
Ok.
>> c) Make the documentation available
>>
>
> In a somewhat related question, would it be possible to have a copy of
> the Haiku User Guide html pages under the haiku-os.org domain? There are
> many planes in the website where I would like to link to the User Guide,
> and I would like it to be to a regular http:// address and preferably in
> the same domain.
That would be the right thing to do.
> I am really sorry that I am sending this web-related stuff here, but the
> days go by and I am stuck here because I am not getting any resonance
> from the haiku-web list or the people that signed up for the task.
>
> If this is agreeable, I would like to start from tomorrow (Monday Sept. 7).
I think it can be started later, however, if there is no objection
then we might as wel get to it.
N.
Other related posts:
