<?xml version="1.0" encoding="UTF-8"?>
<news type="array">
  <news>
    <author-id type="integer">38</author-id>
    <comments-count type="integer">0</comments-count>
    <created-on type="datetime">2009-11-16T18:01:26+00:00</created-on>
    <description>Check the changelog :-)</description>
    <id type="integer">220</id>
    <project-id type="integer">54</project-id>
    <summary>Check the changelog :-)</summary>
    <title>Beta 1.0.34 is out </title>
  </news>
  <news>
    <author-id type="integer">38</author-id>
    <comments-count type="integer">0</comments-count>
    <created-on type="datetime">2009-11-14T15:22:28+00:00</created-on>
    <description>Various improvements, check changelog.</description>
    <id type="integer">217</id>
    <project-id type="integer">54</project-id>
    <summary>Various improvements, check changelog.</summary>
    <title>Beta 1.0.32 is out </title>
  </news>
  <news>
    <author-id type="integer">38</author-id>
    <comments-count type="integer">0</comments-count>
    <created-on type="datetime">2009-10-17T12:29:19+00:00</created-on>
    <description>Some fixes + improved mirror support.</description>
    <id type="integer">207</id>
    <project-id type="integer">54</project-id>
    <summary>Improved mirror support.</summary>
    <title>Beta 1.0.31 is out</title>
  </news>
  <news>
    <author-id type="integer">38</author-id>
    <comments-count type="integer">0</comments-count>
    <created-on type="datetime">2009-10-07T18:49:14+00:00</created-on>
    <description>The latest release now includes a dedicated exe file that enables admin to script their repositories.
You can do stuff like 
-configure an xml with paths to your arma installation.
-run a batchfile to run the autorepository builder (can be put in scheduled tasks!)
-have the tool automatically remove old signature files and resign addons (if wanted with an autogenerated key)
-have the tool autocompare your old repository (handy for guys that use a remote ftp server) and automatically upload the new repository to your ftp server
-get logfiles of the building process via mail (you can also CC or BCC them to fellow admins/clanmembers) (it's via SMTP, so requires SMTP server value)
Some sample repository building files are included. 
A manual must still be made, but the xml is not that obscure so admins should be able to get stuff going.

In short this could enable people to just drag whatever addons they want to share with their clan on their server, and then have it automatically or by one click make an AddonSync2009 repository of those files.
</description>
    <id type="integer">204</id>
    <project-id type="integer">54</project-id>
    <summary>Auto-repository builder!</summary>
    <title>Beta 1.0.30 is out (Includes auto repository builder)</title>
  </news>
  <news>
    <author-id type="integer">38</author-id>
    <comments-count type="integer">0</comments-count>
    <created-on type="datetime">2009-09-22T16:52:07+00:00</created-on>
    <description>v28 had a bug that caused downloading from relative repositories to fail.</description>
    <id type="integer">191</id>
    <project-id type="integer">54</project-id>
    <summary>v28 had a bug that caused relative repositories to fail.</summary>
    <title>Beta 1.0.29 is out (fixes critical download bug) </title>
  </news>
  <news>
    <author-id type="integer">38</author-id>
    <comments-count type="integer">0</comments-count>
    <created-on type="datetime">2009-09-18T18:29:12+00:00</created-on>
    <description>Fixes critical download bug (check roadmap for more info)
I've put the v1.0.27 offline.</description>
    <id type="integer">188</id>
    <project-id type="integer">54</project-id>
    <summary></summary>
    <title>Beta 1.0.28 is out  (fixes critical download bug)</title>
  </news>
  <news>
    <author-id type="integer">38</author-id>
    <comments-count type="integer">0</comments-count>
    <created-on type="datetime">2009-09-18T14:48:22+00:00</created-on>
    <description>Makes it easier to mirror a repository

WARNING!: You can now build repositories with relative paths. 
However every version lower then 1.0.27 WILL NOT BE ABLE TO HANDLE THESE REPOSITORIES!
=&gt; If anyone has trouble downloading your repository, make sure they have at least v 1.0.27.

The tool will be able to handle repositories built with lower version numbers, but not the other way around.
</description>
    <id type="integer">187</id>
    <project-id type="integer">54</project-id>
    <summary>Makes it easier to mirror a repository</summary>
    <title>Beta 1.0.27 is out </title>
  </news>
  <news>
    <author-id type="integer">38</author-id>
    <comments-count type="integer">0</comments-count>
    <created-on type="datetime">2009-09-12T19:48:41+00:00</created-on>
    <description>Has a context sensitive helpfile.</description>
    <id type="integer">184</id>
    <project-id type="integer">54</project-id>
    <summary>Has a context sensitive helpfile.</summary>
    <title>Beta 1.0.26 is out </title>
  </news>
  <news>
    <author-id type="integer">38</author-id>
    <comments-count type="integer">0</comments-count>
    <created-on type="datetime">2009-09-09T19:21:05+00:00</created-on>
    <description>Supports HTTP download resumes.</description>
    <id type="integer">181</id>
    <project-id type="integer">54</project-id>
    <summary>Supports HTTP download resumes.</summary>
    <title>Beta 1.0.25 is out</title>
  </news>
  <news>
    <author-id type="integer">38</author-id>
    <comments-count type="integer">0</comments-count>
    <created-on type="datetime">2009-09-01T20:36:24+00:00</created-on>
    <description>Some fixes/features check roadmap.</description>
    <id type="integer">174</id>
    <project-id type="integer">54</project-id>
    <summary>Some fixes/features check roadmap.</summary>
    <title>Beta 1.0.23 is out</title>
  </news>
</news>
