Blueprint assignments for “trunk”

This listing shows the assignment of work for blueprints currently associated with trunk. The drafter is responsible for getting the specification correctly written up and approved. The approver is usually the person who would sign off on the specification.

111 of 11 specifications
Priority Name Definition Delivery Assignee Drafter Approver
5 Essential JUnit coverage of the project is not nearly complete 0 Approved 6 Slow progress Gregory Moyer
5 Essential Instead of lazy loading the properties file, it may be better to have an explicit load. 0 Approved 11 Implemented Gregory Moyer Gregory Moyer Gregory Moyer
4 High Remove the restriction that keys be Enums 0 Approved 11 Implemented Gregory Moyer
4 High Review whether or not the IllegalArgumentException should be thrown rather than caught (with a default value returned) for parsed getters 0 Approved 11 Implemented Gregory Moyer Gregory Moyer Gregory Moyer
4 High Allow importing of properties files 3 Drafting 1 Not started
3 Medium Provide a copy method that takes a File argument 0 Approved 11 Implemented Gregory Moyer
3 Medium Implement a more concurrency-friendly version of ManagedProperties 0 Approved 11 Implemented Gregory Moyer
3 Medium Add ability to check if a properties manager is "dirty" or has been modified since the last save or load 0 Approved 11 Implemented Gregory Moyer
3 Medium Similar to saving individual properties, allow loading of individual properties 0 Approved 11 Implemented Gregory Moyer
3 Medium ManagedProperty is a bad name that does not follow the naming pattern of PropertiesManager 0 Approved 11 Implemented Gregory Moyer
3 Medium Add the ability to save an individual property to a file without saving other properties that may have changed 0 Approved 11 Implemented Gregory Moyer
111 of 11 specifications