Great! Now we can get started on the work for Beta 3. Is it okay if I write
up a blog post announcing the timeline? One of the things I noticed we need
to improve on is communication of timelines, so I'm more than happy to
spread the word to the rest of the community. Should this be under the
"News" section, or the normal Blog-o-sphere?
The Promotion Team are already looking into USBs and DVDs, and I've already
contacted Ryan to let the Inc. know about this as well. We have submitted
quotes to two possible services and are waiting to hear back from them.
Finally, we're finalising the press release so would appreciate any
developers having a look there and fixing any mistakes we've made (i.e.
getting the technical specifics of something wrong). I have yet to include
the list of the most prominent improvements/changes, but that will come
soon.
I also posted on the forums that I need a developer to give a quote
(basically a short statement of what one thinks about the release) but it
seems no one saw that - so any developers on here that are interested?
Thanks,
Jonathan
(jt15s)
On Sun, 13 Jun 2021 at 00:11, Alexander von Gluck IV <kallisti5@xxxxxxxxxxx>
wrote:
June 5, 2021 6:33 PM, "Alexander von Gluck IV" <kallisti5@xxxxxxxxxxx>
wrote:
Good evening!base
I've been hearing growing community consensus for an R1 / Beta 3 release.
I updated https://dev.haiku-os.org/wiki/R1/Beta3/Timeline with a draft
timeline around rolling out an R1 / Beta 3.first
We need to branch R1/Beta 3 and update the Haikuports Builders with the
"release candidate" for the updated app_server code to begin eventhinking
of merging + testing the latest webpositive + webkit2 work / changes
Please provide feedback and let us know if you think it's "time" :-)
I haven't seen any -1 comments. Thus after 7 days i'm considering this one
approved by the community.
https://dev.haiku-os.org/wiki/R1/Beta3/Timeline contains our release time
table.
I can fill in the sysadmin + release coordinator functions, is there
anyone who
wants to fill in the release coordinator in a secondary/backup role?
(Ideally this individual should have contributor level access)
-- Alex
