On Wed, 2008-09-24 at 02:16 +1200, Amos Jeffries wrote: > > > > Lets set a date: 29 September? > > > > Well, I'll call for a partial hold right now. Please only commit bug > > fixes, minor cleanups, and features already on the roadmap for 3.1. > > The rest can be queued for commit post branch. > > > > > 5 days to go and these bits left.... > > > * connection pinning > > I thinking it's been outstanding long enough we should get it into 3.1, > > even if we have to hold PRE1 a week after the branch to stabilize it (or > > test it in PRE1 ?). > > > > Awaiting merge. (1-2 days).
Do we go from trunk to PRE or from trunk to DEVEL? I do not think trunk code is stable enough to be called PRE at this point, so I was expecting DEVEL. Personally, I would just call it 3.1.0 and categorize it as "development" on the web site until we can move it into the stable category (after a few 3.1.x releases). > > * kerberos helper > > Markus has supplied another set of code, I assume its been tested > > externally and just needs a drop-in. > > > > Awaiting re-submission with some alterations. Non-blocker. > > > * eCAP > > > > Awaiting merge submission. > > > * source layout > > > > Started. Non-blocker. > > > * source formatting > > scripts committed for use already, I was planning on starting the > > re-format and testbed run today here. > > Now waiting on completion of other feature code. > > > Other misc stuff which qualifies but need some work if people have time: > > Awaiting a verify: > http://www.squid-cache.org/bugs/show_bug.cgi?id=2433 > > Awaiting a verify test and debug: > http://www.squid-cache.org/bugs/show_bug.cgi?id=2393 > > Awaiting a developer: > * testbed level-02-maximus.opts > opposite of minimal. Everything enabled, leave configure to handle > clashes properly etc. Other important problems: http://www.squid-cache.org/bugs/show_bug.cgi?id=2459 http://www.squid-cache.org/bugs/show_bug.cgi?id=2460 I have asked somebody to work on these for the next 10 days, but I do not know if they will be able to fix them. I can work on them after eCAP. Also, it would be nice to review and commit TCP_RESET propagation patch: http://www.squid-cache.org/bugs/show_bug.cgi?id=2042 Cheers, Alex.
