| Re: [tcf-dev] Is TCF "done" for 1.0 ? |
|
Good ! If we think we are “done” then no extra work after today’s build until 1.0 is expected anyways. I think it would benefit us if we discuss potential planned changes (for risk and appropriateness) before committing them. That’s why I’m in favor of requiring a Bugzilla before committing. Hopefully none of these are needed anyways so the bureaucracy should be small. If we think that we still want to do little cleanups here and there without bugzilla then we’re probably not as “done” as we think and freezing / branching is not quite what we want yet. Thoughts ? Martin From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Stieber, Uwe Hi Martin, From my POV, and if we take the build that will be procduced today night, we are done for 1.0 and can tag and branch (bugzilla #380447). Regarding check-in’s to the 1.0 branch, I’m always for dropping bureaucracy, means I would vote for commit notifications only. Best regards, Uwe J From:
tcf-dev-bounces@xxxxxxxxxxx
[mailto:tcf-dev-bounces@xxxxxxxxxxx] On Behalf Of Oberhuber, Martin Hi all, Having checked TCF against the sim.release requirements, fixed and submitted the IP Log, fixed copyrights and abouts … … it looks to me like TCF is “done” for 1.0, pending only the release review documentation. Is there anything severe still missing from the code base or can we do a build that we call final ? I’d like to get traceability of any changes still occurring to the 1.0 code base from now on.
Would that be satisfied by commit notifications and using the branch, or should we require a bugzilla entry targeted against an “1.0” target milestone for every change, for better traceability ? Thanks, Martin -- Martin Oberhuber, SMTS / Product Architect – Development Tools,
Wind River direct +43.662.457915.85 fax +43.662.457915.6 |