You need to log in before you can comment on or make changes to this bug.
Darren's following request: Hi Chris: While I was reviewing your maturity level tables I realized that we needed to split the *R* category R (release) - out of development, no known bugs, thoroughly tested, completely documented into two new categories: RT (Release - technology) - out of development, few known bugs (all minor), thoroughly tested, widget doc completed RP (Release - product) - out of development, no known bugs, thoroughly tested, all documentation completed This will account for the differences in the documentation and bug management between a 1.99 release and a 2.0 release, for example. -------------------------- From the maturity level xml schema, it is a one second fix. But I realizing that this changes a few things. I have the follow question that need to be consider before this bug is resolved: 1) Is there any complications to the maturity level code in Chameleon? 2) Is there any complications to the maturity level code in Doc Builder? If no to both questions than this bug can close.
from a technical point of view, there is no differentiation between two different release categories and I don't see this as being a value that would make a difference to the end user of the widgets (i.e. they are unlikely to see a difference betweeen minimum maturity levels of RT and RP. But I will add these to the code base anyway. Leaving to Bill to determine if there are any complications in the doc builder. New maturity levels are: MATURITY_TECHNICALRELEASE MATURITY_PRODUCTRELEASE
While the technical distinction between the two levels is not great, I still think there is some. Some users might be more comfortable using a widget if it is included in documents like a tutorial and/or users guide. As well, with even fewer known bugs in PR than in TR, that also might be of help to the user. I agree that the largest "gain" from this distinction is an internal one, I'd still like to make this distinction at this point.
No problems for the doc_builder...updating now.
Fixed in CVS.
