[Apparmor-dev] Developing an AppArmor release schedule

[John Johansen]

AppArmor releases up to this point have been primary driven by SUSE's
release schedule.  With more distributions shippping AppArmor this
must change and the project is going to move to a more regular
development and release schedule.  The goal is to set up a public
schedule, that is guided by all interested parties.

Just what that schedule will look like has yet to be decided, but I was
thinking it would be nice to have regular release every six months.
Of course at this point that is just my suggestion and I would really
like to find what is best for all interested parties.

The specifics of what will be included in the next release will have to
wait until I can finish documenting (at least in a rough form) the work
and directions that have already been taken, and we can get those posted
out to the wiki and to apparmor-dev for discussion.  This will happen
soon but I can't promise a date just yet.

With that said AppArmor has seen enough improvements that we are targeting
a 2.3 (skipping 2.2 to fix some versioning problems) release for mid February.
Unfortunately this release hasn't been properly vetted by the community
and with mid February only a couple of weeks a way, there isn't
a much that can be changed but it does provide a good starting point
for future releases.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
Url : http://forge.novell.com/pipermail/apparmor-dev/attachments/20080125/834a0002/attachment.pgp