Present: Roland, Frank, Yosef, Matt, Ian, Peter, Josh, Philipp
Josh and Yosef report problems calling the toll free number from a phone.
Tickets: * remove snprintf implementation in Cactus since Cactus requires (and tests for) C99 which always provides snprintf * patch to abort early in CST has become redundant due to Erik's recent efforts to build ExternalLibraries along with normal thorns * Jenkins now works again
Ticket system: * desire to have screening of incoming tickets * talking points: ** The screening process will assign a priority to the ticket ** Description of priorities *** blocker - Cactus does no longer build *** critical - at least one thorn always fails to run *** major - needs to be fixed before release or documented in release notes *** minor - may or may not be fixed before release *** new - the initial priority created by trac to search for unclassified tickets ** Desire to have ticket status "Looked at"/"Triaged" instead of "Confirmed" that signifies that screening was done. ** Assign it to a person likely being able to help with it. This should be based on common sense, and assignation does not imply an obligation to provide a fix but is kindly requested to look at it. ** milestones to be used only during the release process to mark tickets we want to push until the release * Ian tasked with testing these ideas with ~10 existing tickets * Frank checked automated assignments are reasonable ** Change GetComponents from Eric Seidel ** Remove automated assignment from simfactory ** add "Server infrastructure" component to take over ET trac but contain all server issues * custom queries on trac ticket ** new section with most common predefined custom queries *** changes in the last week *** pending review ** new section with queries useful to review tickets ** new section with queries useful before the release
Jenkins: * ask Steve to check on CCT Jenkins slave * downgrade Caltech Jenkins slave
Yours, Roland
On Mon, Dec 08, 2014 at 06:28:39PM +0100, Roland Haas wrote:
- custom queries on trac ticket
I reordered/wrote these. Please have a look at https://trac.einsteintoolkit.org/wiki and comment.
I also checked that emails are sent for tickets that you updated at some point in time if you configured your email address in trac. It also sends emails if tickets are assigned to someone with a configured email address that so far hasn't touched this ticket. It even works to assign a ticket to just an email address (in the sense that this address gets a message about this), although for obvious reasons that is not always such a great idea.
Frank
users@lists.einsteintoolkit.org