Nigel Kukard <nkukard@...> writes: > > On 05/09/12 21:47, Fabio Sangiovanni wrote: > > > > I need to deploy policyd in a production environment. > > I've noticed that version 2.0.11 as downloaded from > http://devlabs.linuxassist.net/projects/policyd/files is affected by some > issues. > > Personally verified: > > > > - wrong query result check in webui's policy-delete.php (prevents delete of some policies). > > - cluebringer.spec not updated with the correct version (2.0.11a) and with wrong filenames (CHANGELOG > instead of ChangeLog) -> prevents RPMs from building successfully (minor problem, but it's still there) > > - wrong quota management (see > http://devlabs.linuxassist.net/projects/policyd/repository/revisions/e6e98822bb8c571f6c05272c884dcdae4858f770 > and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624164) > > This should of prompted another release. I'll have the current 2.0.x > branch spun into 2.0.12 hopefully in the next 24hr. > > > > > Given this, what is, in your opinion, the best (bug free?) version of policyd? What should I use in a > production environment? Should I take a snapshot from the current development branch of 2.1? > > 2.1 has a major cumulative size vs. message size change pending. If you > don't mind a series of SQL updates to bring everything in line 2.1 > should be safe to use, there are no known issues with the git branch. > > > Requirement: it MUST support quotas. > > It's a plus if I can get RPMs (built or downloaded) easily. > > I'll spin both a development snapshot for 2.1.x and a stable 2.0.12 in > the next 24hr. Not entirely sure why this was not done, but I'll sort it > out. > > -N > >
I have set up the latest development snapshot (v2.1.x-201205100639) in our Zimbra_7.2 production environment with 4000+ accounts. Zimbra7 still has bundled the latest stable 2.0.10 release, so I had to do some additional work to integrate policyd_2.1 with Zimbra. I'm actually using (only) the quotas feature without problems so far. My question for Nigel is: can you please provide some more clues about the SQL changes regarding the message size? TIA, Fabrizio _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
