Release Planning
From FrugalWiki
Introduction
After the release of 0.6, there is a need for a new way of planning features for the next release of Frugalware so that we can let others know what we wish to implement and will allow for better discussion of these features. Planning features like this will allow others to find problems with an implementation plan for something that others may not have spotted. This will mean that things will have less bugs by the time they are implemented because of being checked by other developers. This idea is similar to the Blueprints system used to create specifications on Launchpad.net, which Ubuntu uses.
How it works
We start with the idea. I have the idea of replacing sysvinit. The first step is for me to think of a name for the specification. This name has to be in wiki format because it will be written into this wiki. The name here will be ReplacementInit. So, I navigate to http://wiki.frugalware.org/Features/ReplacementInit and write the specification, based on SpecTemplate. Once I have written it, I will mention it on the devel IRC channel. Then discussion can take place on the discussion page of the specification (click the discussion tab above it). Once all discussion has taken place and the developers concerned have no issues remaining with it, it's status can be set to approved, and it can be implemented. Finally, when it has been implemented, the status is set to completed, and a completion date should be added.