Discussion of the new fields of Codev WebForm
I propose to add some values to the
TopicClassification field to specify a more "formal"
status workflow:
What seem to be the usage pattern now that TWiki is a more mature phase (in the initial phase, the Core team was busy
developing and issuing versions):
- 1 People (out of core team) contribute wishes or bug reports
- 2 Agreement is reached on how to fix it
- 3 A fix/enhancement is proposed as tentative patch & Some comments are made on the principles of it
- 4 Some comments are made after use on real sites, and patch is modified, etc, etc...
- 5 Patch is in TWikiAlphaRelease
- 6 Patch is in TWikiAlphaRelease and should be applied asap by production sites (bug fix, security fix, very useful enhancement) It should be given a patch number to specify the order in which patches should be applied, and thus people could identify their versions as BeijingPatch37 ,etc...
One also could add a file in the TWiki distrib, Patchlevel, where all applied patches would be listed, one per line. Patches would also modify this file to append their name there...
(If you add / modify these states please do not change the existing numbers)
The natural states of a contributed bugfix could thus be: 3->4->6 for simple ones, 1->2->3->5 for major features, etc...
One could thus set up a page listing all the topics in state
6 to know which ones to apply
to production sites.
My proposal for the naming of these 6 states is: (feel free to debate/modify)
Thus, the "job" of a Beijing TWiki maintainer would be to monitor (or to be mailed the changes, ideally)
all the topics with
TopicClassification field being
PatchToBeijing
--
ColasNahaboo - 12 Apr 2003
Overall, sounds like a great idea, especially the step 6 and auto mailing to TWiki maintainers!
--
RandyKramer - 13 Apr 2003