Some questions for us to think about:

• Who is our target user and what do they use FlexWiki for?
• What priority of bugs will we fix?
• Will we add features? Which ones?
• Are there other criteria? Test coverage?

Thoughts About Implementing New Features

It seems that a SQLProvider will be our big feature in FlexWiki 2.0, but along the way several features have been implemented as well that add value, however, we need to be sure that we aren't delivering half features. For example, the recent ChangeNoteFormSelectFieldPresentation details a recent addition that gives combo and listbox functionality to the form output in WikiTalk, but there are clearly other things that should be done to provide a complete implementation of form support in WikiTalk, like checkboxes and radio buttons. I'm sure that there are other areas like this that are mostly implemented, but not feature complete, so we should have a good review of existing functionality and make sure we're giving a good solid implementation.

Perhaps we should use this space to make a ListOfBugsToFix and a ListOfFeatureRequestsToImplement.

The other area that we've started talking about on the FlexWikiMailing list for CoreDevelopers is using FxCop in the build process. Is this another area that we want to include in our drive for a SolidRelease? -- DerekLakin [1-Feb-2005]

• The build process improvements are now complete, right? -- TommyWilliams [15-Feb-2005]
• Yes. FxCop is run on every checkin, as is a complete SqlProvider database setup and tests. DerekLakin is working on getting the FxCop project whipped into shape in terms of exclusions, but a rough cut is there now. -- CraigAndera 2005.02.15

Triaging bugs

What will the bug triage process look like? If we look at the criteria for bugs below, some set of people have to make judgments about at least two of the cases (affects core functionality and affects majority of audience). And what about the repeatable requirement? Do we have coverage of all the supported platforms? What are the supported platforms? Is there a TestMatrix? -- TommyWilliams 15-Feb-2005

Suggested Criteria

Feature Requests

1. Documented in the FeatureRequestTracker
2. Completes an existing partial feature implementation, e.g. form elements (see above).
3. Adds major new functionality that will form part of the 'sales pitch' for FlexWiki 2.0, e.g. SQLProvider.
4. Dramatically improves the user experience, e.g. a web based installer.

Bugs

1. Documented in the BugTracker
2. Repeatable.
3. Affects core functionality.
4. Affects the majority of the TargetAudience for FlexWiki.

Build System

1. Improves coverage of existing functionality through unit testing.
2. Adds unit tests to areas of functionality not yet tested automatically.
3. Improves overall quality of code, e.g. using FxCop.

Documentation

Any documentation that can be added to document existing features is a good thing and becomes more important as we approach the SolidRelease. This is especially the case in areas such as installation and WikiTalk that appear to be the areas that cause the most confusion.

I'm sure this isn't a complete list, but it gives us somewhere to start from. -- DerekLakin [2-Feb-2005]