- implement unit test for new XMLDescriptionData object
- register new code in the commit-hook
- add new triggers for the new test code and the new object
- add new unit test to existing triggers
- implement the getDescriptionInfo method in the XML object.
  The method uses the new KIWIXMLDescriptionData object, which
  gets created based on the data in the imageConfig datastructure
- implement unit test for the getDescriptionInfo method
- v5.04.01 released
- don't create an instance of KIWILog other than the
  global one in KIWIXMLDescriptionData
- don't create an instance of KIWILog other than the
  global one in: KIWILocator,KIWIRuntimeChecker and
  KIWIXMLValidator
- added support for filesystem mount options during image
  build and later to become stored in the fstab file. The
  type attribute <type ... fsmountoptions="..."/> has been
  added, this is related to (bnc #764042)
- fixed getSize and getBlocks functions to calculate with
  integer values. In addition to that the value of getBlocks
  was formerly passed to a dd call but this has changed to a
  qemu-img call. the seek value in the prior dd call was
  offset -1 which is wrong when using qemu-img
- added support for btrfs seed live ISO images. btrfs supports a
  nice COW machinery which allows us to point all write operations
  to a seed device. A similar technique is used with the clicfs
  filesystem but this one works in userspace via fuse. I have
  changed the suse-12.2 JeOS template provided by kiwi to use the
  new btrfs seed way. Of course the clicfs way also still exists.
  In order to use btrfs seed devices your iso type should look
  like the following example:

  <type image="iso" ... flags="seed" fsmountoptions="compress=lzo">
      <size unit="M">400</size>
  </type>

  I got best results with lzo compression. One downside; up to now
  it's not possible to forecast/calculate how much size the btrfs
  image really will need. Thus the calculation kiwi does is in most
  cases too big for small images and for big ones sometimes too
  little. At the moment it's a try and error game to find
  out the minimum required size.

  The implementation add a ramdisk device as seed device to the
  btrfs mount and remount it read-write. This has worked fine
  and stable with the openSUSE 12.2 kernel (bnc #764042)
- changed the suse-12.2 JeOS template provided by kiwi to
  switch from clicfs to the new btrfs seed way (bnc #764042)
- netboot: added function pxePartitionSetupCheck() which is
  used to validate the PART information whether the requested
  partition sizes can be reached according to the size of the
  disk. This implements the request in (bnc #771592)
- make sure dropbear keys are installed with correct permissions
- fixed rpmlint warnings about hidden and empty files
- moved startDropBear() prior to the ELOG_BOOTSHELL check
- remove cached repos for a new build. The repo setup for the
  package managers smart and yum are cleaned up at the end of
  each build by resetInstallationSource(). For zypper we makes
  an exception here and keep the repo setup for performance
  reasons. Thus at the beginning a a new prepare run we should
  clean up the repo files to rebuild the repos as they are
  specified in the kiwi XML description
- update size for btrfs filesystem when building JeOS 12.2 iso
- changed support for dropbear ssh. we don't provide our own
  keypair but allow to integrate a user public key from the
  pxe server. The key must be stored in <server-root>/KIWI
  and has to be named: debug_ssh.pub. for the default tftp
  download method this would result in the following path
  on the pxe server: /srv/tftpboot/KIWI/debug_ssh.pub
- update rhel-* oemboot code to the current suse-* oemboot code
- DB: update docs about dropbear based ssh access into the boot image
- DB: rebuild documentation
- v5.04.2 released