1.2.3 freeze in effect

As of today I am respecting the freeze. Please do the same. Do not apply
any work to the tree unless the work fixes a bug we are tracking and
the work has been put into patch form and uploaded to the bug being
worked on.

Threatening a freeze did have the desired effect on all of you. Because
we almost doubled the number of bugs attached to the release. Thank you
all for taking the time to get our attention and get the bugs noticed.

The current 1.2.3 release bugs:
http://opie-bugs.oszine.de/view.php?id=1837

Bug 1840 is probably going to get fixed today. The inability to compile
will make sure it gets fixed right now. Please try the patch that is
currently attached. It should be complete for building on ARM.

Bug 1839 looks simple. I don't have any problem applying the patch there
soon. Speak up if you disagree.

Bug 1838 is controversial. And may get dropped. Dmitriy is for all
intents and purposes the bluetooth maintainer and if he doesn't like the
patch, we need a best effort to get it into a shape that he can live
with. I also think the patch is a bit hamfisted. If someone from the
distros popped up and could tell us the availability of
/etc/sysconfig/bluetooth. It would help the patch's case. On that note,
Dmitriy - the h2200 port of Opie really needs a better way of figuring
out what to do about bluetooth then by reading the raw MTD device for
whatever the bootloader says is there. That is just plain painful. So we
do need a compromise.

Bug 743 and 1829 do not have patches yet. At this point I am sort of
expecting Paul E. to coordinate those bugs. Paul, speak up if you need
help etc.

Thanks everyone. Let's see if we can wrap this up in record time and let
the distros get to using this release. It ought to be a good one.

E

-- 
Erik Hovland
mail: erik_at_hovland.org
web: http://hovland.org/
PGP/GPG public key available on request