4 Mar
2012
4 Mar
'12
9:01 p.m.
This is part of the plan already. :-) I envision at
least part of that to be a soft freeze, where any bugs found during the freeze can
be patched, but nothing else can be touched.
I like that idea. With the envisioned R14 release date still a couple of months down the
road, a short soft freeze now will allow us all to stabilize and verify all packages build
against TQt3. In other words, everybody stops tweaking and tinkering for a few days and
only verify the building process. :)
Right now seems that every other day or so one package or another will not fully build
without an error. When we get through the temporary freeze, we can focus on the bugzilla
but all have comfort knowing that tqt build issues have been addressed.
Also, I hope that once everything is building again on
TQt3
(which should be very quickly), the other developers here will start
looking at the bugtracker again and send in more patches. ;-)
Please send the word when your first pass is complete. I am supposed to push some minor
patches but have been waiting to update my local tree to run one more build pass. I did
not want to waste time trying to build with known build issues. :)
Actually, until last week I was building all core, main (including tdebindings), and a
dozen Applications packages with only a few build issues (bug reports filed). My big
obstacle has been building the tdebindings support packages.
I propose a team goal that R14 is not released with any unresolved Blocker, Critical, or
Major bug reports. Possibly even add 40 to 50% of the Normal reports too. Is this doable?
Agreeable?
Darrell