Blueprint helps you track the implementation of a feature. This is especially important for features that have been set as goals for a particular release - the release management team needs to know where you stand as freeze and release dates approach.

Implementation Status Values

The "implementation status" of a feature can take one of several values:

• Unknown. We have no information on the implementation of this feature. This is the default starting point for newly registered feature specifications.

• Deferred. There is no chance that this feature will actually be delivered in the targeted release. The specification has effectively been deferred to a later date of implementation.

• Needs Infrastructure. Work cannot proceed on this feature, because it depends on infrastructure (servers, databases, connectivity, system administration work) which has not been done. It would be unusual to use this state, because in general development work itself does not depend on outside infrastructure. Don't confuse this state with the Deployment state, where the code is reviewed and approved but not yet deployed on production servers.

• Blocked. Work cannot proceed on this specification because it depends on another feature in a different specification which has not yet been done. Note: the other specification should be listed as a blocker of this one so that Launchpad can calculate dependency trees and figure out the right roadmap for feature implementation.

• Started. Work has begun on this feature, but has not yet been published except as informal branches or patches. No indication is given as to whether or not this work will be completed for the targeted release.

• Slow progress. Work has been slow on this item and it has a high risk of not being delivered on time. Help is wanted on direction or assistance is needed with the implementation of the feature.

• Good progress. This feature implementation is making good progress and is considered on track for delivery in the targeted release.

• Beta. The code for this feature has reached the point where a beta version that implements substantially all of the required functionality is being published for widespread testing, in personal package archives or a personal release, but the code is not yet in the main archive or mainline branch. Testing and feedback are solicited.

• Needs Code Review. The developer is satisfied that the feature has been well implemented, and is now ready for review and final sign-off on the feature, after which it will be committed and marked implemented.

• Deployment. The work contemplated in this specification has been done, and can be deployed in the production environment, but the system administrators have not yet attended to that. Note: the status whiteboard for the specification should include a ticket reference for the deployment request.

• Implemented. The green light! This functionality has been delivered for the targeted release, the code has been uploaded to the main archives or committed to the targeted product series, and no further work is necessary. We are DONE!

Subscribers will be notified when you change the implementation status of any of your specifications.