Re: Squid 3.5 release timetable
On 08/25/2014 06:28 AM, Amos Jeffries wrote: > On 23/08/2014 9:34 a.m., Amos Jeffries wrote: >> On 23/08/2014 6:02 a.m., Alex Rousskov wrote: >>> On 08/21/2014 11:54 PM, Amos Jeffries wrote: Update: * FTP and Kerberos patches are in and building fine. (build farm has some internal issues clouding the state) * I am punting Bearer and Parser-NG off into 3.6 series. Some design decisions may take a while to resolve and re-audit. * PROXY protocol and Splice/Peek appear to be almost done with audit. So if those last two can be pushed onward this week I would like to branch once they are merged and the build farm gives them a mostly-blue pass rate. >>> >>> What about the boilerplate updates? I think it would be best to do them >>> before branching as they are another example of simple changes affecting >>> a lot of files. I will try to find the time to revisit that project next >>> week. >> >> Ah, right. If you could at least check and update that list of >> authorships we have permission to move blurbs for I can throw small bits >> of time at the incremental updates. >> Would a comment in the script listing dates as to when each author gave >> permission be doable to make this less of a big ask? > Sorry, another followup. I'm seeing "Claim: Duane Wessels" showing up > already and I've only checked a few bits. It might be worth chasing him > up for permission as well. Yes, I got an explicit confirmation from Duane today. Alex.
Re: Squid 3.5 release timetable
On 23/08/2014 9:34 a.m., Amos Jeffries wrote: > On 23/08/2014 6:02 a.m., Alex Rousskov wrote: >> On 08/21/2014 11:54 PM, Amos Jeffries wrote: >>> Update: >>> >>> * FTP and Kerberos patches are in and building fine. >>> (build farm has some internal issues clouding the state) >>> >>> * I am punting Bearer and Parser-NG off into 3.6 series. Some design >>> decisions may take a while to resolve and re-audit. >>> >>> * PROXY protocol and Splice/Peek appear to be almost done with audit. >>> >>> So if those last two can be pushed onward this week I would like to >>> branch once they are merged and the build farm gives them a mostly-blue >>> pass rate. >> >> What about the boilerplate updates? I think it would be best to do them >> before branching as they are another example of simple changes affecting >> a lot of files. I will try to find the time to revisit that project next >> week. > > Ah, right. If you could at least check and update that list of > authorships we have permission to move blurbs for I can throw small bits > of time at the incremental updates. > Would a comment in the script listing dates as to when each author gave > permission be doable to make this less of a big ask? > > Amos > Sorry, another followup. I'm seeing "Claim: Duane Wessels" showing up already and I've only checked a few bits. It might be worth chasing him up for permission as well. Amos
Re: Squid 3.5 release timetable
On 23/08/2014 6:02 a.m., Alex Rousskov wrote: > On 08/21/2014 11:54 PM, Amos Jeffries wrote: >> Update: >> >> * FTP and Kerberos patches are in and building fine. >> (build farm has some internal issues clouding the state) >> >> * I am punting Bearer and Parser-NG off into 3.6 series. Some design >> decisions may take a while to resolve and re-audit. >> >> * PROXY protocol and Splice/Peek appear to be almost done with audit. >> >> So if those last two can be pushed onward this week I would like to >> branch once they are merged and the build farm gives them a mostly-blue >> pass rate. > > What about the boilerplate updates? I think it would be best to do them > before branching as they are another example of simple changes affecting > a lot of files. I will try to find the time to revisit that project next > week. Ah, right. If you could at least check and update that list of authorships we have permission to move blurbs for I can throw small bits of time at the incremental updates. Would a comment in the script listing dates as to when each author gave permission be doable to make this less of a big ask? Amos
Re: Squid 3.5 release timetable
On 08/21/2014 11:54 PM, Amos Jeffries wrote: > Update: > > * FTP and Kerberos patches are in and building fine. > (build farm has some internal issues clouding the state) > > * I am punting Bearer and Parser-NG off into 3.6 series. Some design > decisions may take a while to resolve and re-audit. > > * PROXY protocol and Splice/Peek appear to be almost done with audit. > > So if those last two can be pushed onward this week I would like to > branch once they are merged and the build farm gives them a mostly-blue > pass rate. What about the boilerplate updates? I think it would be best to do them before branching as they are another example of simple changes affecting a lot of files. I will try to find the time to revisit that project next week. Thank you, Alex.
Re: Squid 3.5 release timetable
[.. status] > So if those last two can be pushed onward this week I would like to > branch once they are merged and the build farm gives them a mostly-blue > pass rate. +1 -- Kinkie
Re: Squid 3.5 release timetable
Update: * FTP and Kerberos patches are in and building fine. (build farm has some internal issues clouding the state) * I am punting Bearer and Parser-NG off into 3.6 series. Some design decisions may take a while to resolve and re-audit. * PROXY protocol and Splice/Peek appear to be almost done with audit. So if those last two can be pushed onward this week I would like to branch once they are merged and the build farm gives them a mostly-blue pass rate. Amos
Re: Squid 3.5 release timetable
On 07/29/2014 10:53 AM, Alex Rousskov wrote: > On 07/28/2014 11:53 PM, Amos Jeffries wrote: >> On 29/07/2014 6:22 a.m., Alex Rousskov wrote: >>> On 07/24/2014 10:37 PM, Amos Jeffries wrote: >>> If any of you have patches lined up for commit or about to be, please reply to this mail with details so we can triage what gets in and what can hold off in audit. >>> Here are some of the bigger items on the Factory plate: >>> * Native FTP support (works great; still working on class renaming) >> Can you get that to audit this week? > I do not know the answer, but I am working on making that happen right now. Status update: Significant progress during the last few days. The branch should be ready for audit this week. Alex.
Re: Squid 3.5 release timetable
On 07/28/2014 11:53 PM, Amos Jeffries wrote: > On 29/07/2014 6:22 a.m., Alex Rousskov wrote: >> On 07/24/2014 10:37 PM, Amos Jeffries wrote: >> >>> If any of you have patches lined up for commit or >>> about to be, please reply to this mail with details so we can triage >>> what gets in and what can hold off in audit. >> >> >> Here are some of the bigger items on the Factory plate: >> >> * Native FTP support (works great; still working on class renaming) > > Can you get that to audit this week? I do not know the answer, but I am working on making that happen right now. > FYI there are several goal metrics informing the decision to branch: > > * major user visible features/changes > - Going by user visibility are: Large Rock, Collapsed Forwarding, and > helper *_extras. Possibly also eCAP 1.0. AFAICT, only Large Rock and perhaps helper extras were frequently requested or needed (by more than a handful of users). The pending Native FTP and Peek-and-Splice are major user visible features with lots of requests/need behind them. Only when taken together, they constitute enough benefit to outweigh release maintenance/porting overheads IMO. > * annual stable cycle, (aka. ensuring sponsors wait no more than 1 year > for their features to get into a stable production release) > - initial 3.5 features are almost at 10 months now, even if they are minor. I agree with the goal, but please keep in mind that delaying major features by two years to release minor features in one year is likely to reach the opposite of the stated goal of pleasing feature sponsors. And if the Squid Project decides to switch to the annual cycle, we should publish the freeze dates a little more than a week in advance! HTH, Alex.
Re: Squid 3.5 release timetable
On 29/07/2014 6:22 a.m., Alex Rousskov wrote: > On 07/24/2014 10:37 PM, Amos Jeffries wrote: > >> If any of you have patches lined up for commit or >> about to be, please reply to this mail with details so we can triage >> what gets in and what can hold off in audit. > > > Here are some of the bigger items on the Factory plate: > > * Native FTP support (works great; still working on class renaming) Can you get that to audit this week? > * Peek and Splice (now with SNI; probably ready but may need polishing) > * StoreID via eCAP/ICAP (waiting for audit or Store-ID naming comments) > * on-disk header updates or Bug #7 (probably more than two weeks out) Bug #7 is squid-2.7 parity fix, so a candidate for backporting. > * Store API polishing (no ETA; depends on bug #7) > * post-cache REQMOD support (may be available late August 2014) > > > Judging by the trunk items listed on the RoadMap wiki page, the only > major v3.5 improvement already available is Large Rock, so getting at > least the first two items in would be necessary to justify the > maintenance/porting overheads of a new Squid version IMO. Thank you for that list. FYI there are several goal metrics informing the decision to branch: * major user visible features/changes - Going by user visibility are: Large Rock, Collapsed Forwarding, and helper *_extras. Possibly also eCAP 1.0. - This has been the main criteria previously however after board discussions I am convinced to give this lower priority and I am no longer waiting on a particular feature count threshold. What we have now seems good enough combined with the below criteria. * annual stable cycle, (aka. ensuring sponsors wait no more than 1 year for their features to get into a stable production release) - initial 3.5 features are almost at 10 months now, even if they are minor. * significant LOC change between stable and beta - just over 33% of squid right now (91K/271K LOC). * bugs and general stability - we have a record low number in both 3.HEAD and 3.4 to work on right now. Amos
Re: Squid 3.5 release timetable
On 07/24/2014 10:37 PM, Amos Jeffries wrote: > If any of you have patches lined up for commit or > about to be, please reply to this mail with details so we can triage > what gets in and what can hold off in audit. Here are some of the bigger items on the Factory plate: * Native FTP support (works great; still working on class renaming) * Peek and Splice (now with SNI; probably ready but may need polishing) * StoreID via eCAP/ICAP (waiting for audit or Store-ID naming comments) * on-disk header updates or Bug #7 (probably more than two weeks out) * Store API polishing (no ETA; depends on bug #7) * post-cache REQMOD support (may be available late August 2014) Judging by the trunk items listed on the RoadMap wiki page, the only major v3.5 improvement already available is Large Rock, so getting at least the first two items in would be necessary to justify the maintenance/porting overheads of a new Squid version IMO. HTH, Alex.
Re: Squid 3.5 release timetable
Sounds good to me. On Fri, Jul 25, 2014 at 6:37 AM, Amos Jeffries wrote: > As luck would have it today is exactly 1 year since the first patch was > held in trunk for 3.5 series release. > > Below is my current plan. Any objections please speak up. > > > 1) Branching: > > I hope this can be done next weekend. August 1-3, maybe the week after > if there are delays. > > We have enough features to make it useful even though some of the larger > projects have not made it in. > > However, to minimize work in stage-2 trunk needs to be relatively stable > before this happens. If any of you have patches lined up for commit or > about to be, please reply to this mail with details so we can triage > what gets in and what can hold off in audit. > > Note that patches applied after branching may still get to 3.5, but will > have to be stable in trunk first. > > Patches that are welcome any time: > - documentation updates > - security bug fixes > > > 2) Documentation and stability testing > > After branching we need to do as much testing as we can throw at the new > branch and update any missing documentation. > > Most of the documentation is already done. So its just a scan through to > check for missing or incorrect bits. > > > 3) 3.5.0.1 > > I am hoping this can be done by the end of August. Will happen whenever > step-2 is completed. > > > Stable) as usual depends on bugs > > 2 bugs explicitly on 3.HEAD within the 3.5 development period are > blocking stable release until fixed or determined non-critical. > > 12 major or higher bugs in 3.4 seem worthy of blocking 3.5 stable for a > bit to get resolved. > > We have 60 other major bugs outstanding across all Squid versions that > should be resolved ASAP if at all possible. > > > > > Projects I am aware of that are potentially coming up for commit over > this period: > > * Kerberos autoconf updates > - assuming the current rewrite patch > > * PROXY protocol > - assuming the current partial support patch > > * Peek-n-Splice > - assuming it is relatively isolated changes and well tested already > > * StoreID via eCAP/ICAP > - I'm not sure what this is waiting on. > > > Amos -- Francesco
