ok!  Here's what I see in bugzilla right now:

 ID      Sev     Pri     OS      Assignee        Status          Resolution     
 Summary
6077    maj     P1      All     [email protected]     NEW             
fix failing tests
6131    maj     P1      All     [email protected]     NEW             
Makefile.PL is
doing evil things to detect DESTDIR
6139    maj     P1      All     [email protected]     NEW             
remove
"rulesrc" external from SVN tree
5553    nor     P1      All     [email protected]     ASSI
                MIME_BASE64_TEXT does not handle charset properly
5871    enh     P1      All     [email protected]     REOP            
need docs for
new '--filter-retries' spamc switch

[so those are the 5 P1s.  these are all things that should be done
before a release, but none of them are blockers IMO.]

4949    nor     P2      Free    [email protected]     NEW             
spamd shutting
down when unable to fork new processes
5591    nor     P2      Sola    [email protected]     NEW             
make test
fails at spamd_hup test on Solaris 9, 10
6132    enh     P2      All     [email protected]     REOP            
FreeMail plugin

[would be nice to get done but again not blockers.]

everything else on the 3.3.0 milestone can be pushed off if nobody
gets the tuits to do them.
I think we could conceivably start the 3.3.0 release process soon....
paging Warren ;)

How's about I cut an alpha at the end of this week?

--j.


On Wed, Jun 24, 2009 at 23:00, Justin Mason<[email protected]> wrote:
> On Wed, Jun 24, 2009 at 21:37, Justin Mason<[email protected]> wrote:
>> On Wed, Jun 24, 2009 at 21:21, Theo Van Dinter<[email protected]> wrote:
>>> fwiw, the process used to be:
>>> - beta releases to get things stabilized
>>> - use a beta release to do mass-check runs
>>> - generate scores with mass-check data and submit to svn
>>
>> I think we may be able to simplify that, now that Daryl's system is
>> generating scores weekly...
>>
>> Also one hard part that we need to do is finish the "no rules in main
>> tarball" work item.
>
> which I've just done ;)
>
> is there anything else that we should sort out before an alpha is viable?
>
> --j.
>
>>> - rc releases to get wider testing w/ scores
>>> - release after rc appear to work

Reply via email to