History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: SFS-9
Type: New Feature New Feature
Status: Open Open
Priority: Minor Minor
Assignee: Unassigned
Reporter: Scott Lawrence
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
SIPfoundry Infrastructre

Add statuses to reflect build problems?

Created: 2004-04-02 21:24   Updated: 2004-04-10 16:48
Component/s: tracker
Affects Version/s: None
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown


 Description  « Hide
This one is really a question - should we change the "Blocker" status to two statuses:

"Build Failure" which means that this blocks the build from completing - a very serious situation, since it potentially blocks work unrelated to the change that introduced the problem.

"Build Warning" which means that a new warning message output from the build was introduced. I would like us move to a policy of extreme intolerance for warnings (with lots of them enabled) to enforce very clean and portable coding style; this would let us track these specially.


 All   Comments   Work Log   Change History      Sort Order:
Adam Roach - 2004-04-10 16:48
You can also make the warnings more apparent to the developers before checking code in by making certain the various projects' build systems contain "-Wall -Werror" as their flags (for gcc, at least). Perhaps there should be some sort of best current practice document for project maintainers?