Support/TikiUpstreamPlanning
Tiki Upstream Planning
Looking so far, my very rough, unscientific estimate is that a good day is getting two patches committed. More likely is less than 1.5 on average, to manually resolve conflicts, merge, and do enough BFT to know it's not completely broken.
One wrench in the estimation is that of the almost 900 or so closed (reso fixed or veri fixed) SUMO bugs [1], only around 200 have been triaged so far. I'll deal with this below.
Breakdown of triaged bugs
Bold are blockers in bugzilla.
tiki_feature
- Bug 398246 - no patches or revisions, partially server configurations
- Bug 395271 - patch
- Bug 480223 - revision number
- Bug 465518 - patches
- Bug 412265 - no patches or revision
- Bug 441858 - patch
- Bug 506547 - patch
- Bug 433341 - patch
- Bug 436679 - patch
- Bug 429784 - revisions
- Bug 498001 - patch, revisions
- Bug 492697 - patch, revisions, parallel work in tiki
- Bug 452830 - patch, sql
- Bug 465029 - patch, revision
- Bug 509864 - patch, revision
tiki_bug
- Bug 514244 - NEW, untargeted
- Bug 429529 - patch, revision
- Bug 512120 - patch, not in SVN
- Bug 485557 - revision, possibly fixed in tiki
- Bug 484100 - patch, revisions
tiki_fixed
21 bugs. At some point, will need to check that implementations are compatible.
tiki_triage
38 bugs. Not sure who's on this.
Untriaged bugs
A bugzilla search for closed (veri fixed or reso fixed) bugs in SUMO excluding Chat and Mobile yields 885 bugs ([2]).
Using the current percentages as a guide, there's a rough estimate of around 85 bugs to upstream, instead of the 20 we have triaged so far.
| Component | Triaged Bugs | % of all Triaged Bugs | Estimated total (% * 885) |
|---|---|---|---|
| tiki_feature | 15 | 7.18% | 64 |
| tiki_bug | 5 | 2.39% | 21 |
| tiki_triage | 38 | 18.18% | 161 |
| tiki_fixed | 21 | 10.05% | 89 |
| sumo_triage | 15 | 7.18% | 64 |
| sumo_only | 115 | 55.02% | 487 |
That would also leave around 160 bugs to check in Tiki.