Get a Preview of the Preview….
BeOS PREVIEW RELEASE PORTING LAB
——————————–
Be Developer services is working on setting up a Preview Release porting
lab to help port applications to the Preview Release as quickly as
possible. Applications written for DR8 will not be binary-compatible with
the DR9 release, thus developers will need to recompile their code and make
some modifications in order to take advantage of new functionality. The
Preview Release is the first release in which forward compatibility will be
a priority (and thus the last release to break everything.)
If you want to participate in a porting lab, then please send a message to
devservices@be.com. The lab will be held in March and early April, and as
the date approaches, we’ll get more specific. But since we expect this
space to be limited and in high demand, you’ll want to reserve space now.
This lab is intended for developers who intend to ship a product that is
for purchase with the Preview Release and for whom timing is critical. The
lab will be on-site at Be in Menlo Park, California, and will be available
for a two week period.
Direct Access
BeOS BUGS ARE NOW ON-LINE
————————-
http://www.be.com/developers/bugs/
The BeOS isn’t perfect.
We’ve been collecting bugs from developers for a long time, and now we’re
offering some feedback on the status of the publicly available bugs in our
database. Before you dive into the bugs, please take a moment to read the
document at http://www.be.com/developers/bugs/ thoroughly, especially the
FAQs at the bottom. Your understanding of the information provided here
really will help everyone using the database.
The two main goals of the Bug reporting area are:
1.Provide feedback on the status of an individual bug submitted by a
developer/user.
2.Enable other users/developers to search the database of publicly
available bugs in the hope that pitfalls in the BeOS can be avoided and
duplicate bugs aren’t submitted.
The Bug Search Form has been set up to facilitate both of these things. A
specific bug can be found by searching for the bug’s Bug Number (assigned
when the bug was submitted).
Multiple bugs can also be found based on certain search criteria on the
form. The bugs displayed using these criteria are only the publicly
available bugs. Publicly available bugs are bugs which developers/users
have submitted via the Bug Report Form and were declared available to the
public.
Publicly available bugs can be browsed in batches of 100 at a time. The
bugs submitted within the last month are also summarized on the New Bugs
page.
PRESS REVIEWS
————-
If your product is approaching completion and you want to get some press
coverage, contact hopwood@be.com and we can put you in touch with members
of the media who are following the BeOS and are looking for the first
products to hit the virtual shelves to review. We can also help coordinate
your efforts with Be’s so that you can take advantage of various events and
announcements Be will be making in the same timeframe.
Thanks for your continued support,
Mark Gonzales,
For all of us here at Be, Inc.
