[asterisk-dev] Next 1.6 beta release?

[Oron Peled]

On Thursday, 17 בJuly 2008, Steve Totaro wrote:
> Someone from Digium said it was pretty much a find and replace operation.
>
> I have done that many times with simple ten or fifteen page documents
> meant for people and invariably something read incorrectly or a slight
> variation from the "find" was left in place.

You are of course correct. Therefore, a review of all changes was
a must anyway.

Luckily, it seems that Digium people used the forced review to clean
a lot of old cruft. While these changes cause short term problems
to everybody, they are going to help us all in the longer term.

Just few examples from the top of my head:
 - Splitting kernel stuff from user space.
 - Dropping the archeology garden of 2.4 kernel support
   and using the saner kernel build system.
 - Rearranging driver code by the layout of kernel tree.
   BTW: if I make two symlinks from a linux kernel tree
        (include/dahdi, drivers/dahdi) I can build Dahdi
        as part of the kernel (make xconfig/menuconfig et.al)
 - Cleanup the crazy channel allocations (mentioned in another
   post). E.g: a single E1 span would allocate 31 *contiguous*
   structs of zt_chan -- each taking a bit more than half a page.
   This means 31 contiguous pages!
 - Drop old backward compatibility stuff (V1, V2 ioctls...)

I'm sure the decision to do these things instead of "only string replace"
wasn't easy (deadlines etc.) but it was a good one (since as you
pointed, even simple s/// would cause some problems).


-- 
Oron Peled                             Voice/Fax: +972-4-8228492
oron at actcom.co.il                  http://www.actcom.co.il/~oron
Protect your digital freedom and privacy, eliminate DRM, learn more at
http://www.defectivebydesign.org/what_is_drm