Hi,

It's been long since I last tried to release v0.2 of mod_mbox, without
success. The bug fixed tonight made me focus again on mod_mbox and I
really would like to see things changing and moving on.

Recently, I've been working on cleaning up the directory structure of
the module's source code in a 'surgery' branch. Today, this work is
done and the branch's code compiles, installs and works fine here at
home. Please not that the functionnal code is the same as in mod_mbox
trunk/, including tonight's bugfix.

mod_mbox still needs a lot of improvements as shown in the STATUS file.
But since current code is mostly what came out my Summer of Code, I
would like to see it released before continuing.

Before releasing mod_mbox, we need the work done in the surgery branch
back to trunk. So, unless there is any objections to it, here it what
I'll do in the next few days :

 - Move the scripts/ directory one level up, outside of the branches/
   tags/ trunk/ directory shema. These scripts are not part of the
   module's source code, they do not need to be under it's versionning
   (they're not even include in releases anyways).
 - Merge the surgery branch back to trunk
 - Create a 0.2.1 tarball and call for a vote on releasing it.

In the best case, mod_mbox-0.2.1 will finally come out and I'll continue
hacking on the module ASAP.

Regards,
- Sam

-- 
Maxime Petazzoni (http://www.bulix.org)
 -- gone crazy, back soon. leave message.

Attachment: signature.asc
Description: Digital signature

Reply via email to