CndProcess

Revision as of 14:20, 8 December 2009 by Gorrus (Talk | contribs)

CND Development Process Improvements

Issues

  1. to hard to track regressions
  2. impossible to track tools compatibility

Solution

  1. more unit tests
  2. automated test system
task status
involve different platforms done
track I18N warnings done
static code checks done
get to zero (fix all tests on all platforms)
current notifications are too distracting fixing (AV)
collect test coverage data

OLD

Rules

  1. Compiler warnings highlighting and other hints in the IDE (Tools/Options/Editor/Hints) must be turned on
  2. Deprecation compiler warnings must be fixed asap or filed as P2 bugs.
  3. "Unchecked" compiler warnings must be fixed asap or filed as P2 bugs. (@SuppressWarnings("unchecked") should only be used with extra comment)
  4. I18n warnings must be fixed asap or filed as P2 bugs.

Goals being solved

  1. Improve predictability
  2. Have more time to stabilize release
  3. Early catches of design flaws, error prone code and other issues
  4. Better maintainability of our code base
  5. Early discovery of regressions

Ideas

idea status
Code Style unification. As base we gonna use standard Java guideness. Someone volunteered to look for a tool to autocheck this.
Ask another NetBeans groups about their "best practices" for process (VV)
More QA metrics and tests lovely presented in ICP
Code Reviews
Design Reviews (schedules, specifications) -- as we tried at the beginning of last cycle but not really used.

Proposed rules to follow

High priority

  1. we should have 0 "unevaluated" FindBugs warnings from "tracked" category (at the bottom of Incremental builds)

Medium priority

  1. follow Java Code Conventions, as soon as we have CheckStyle we should have 0 style warnings

Links

Incremental builds

Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo