Arthur Clemens added "Wating for Extension Release" in bugs.
And people have started using this also for default plugins and for extensions that will never be released like BuildContrib
The result is that I can no longer auto generate the bug list for the release note which is the whole purpose of "Waiting For Release".
If I also include "Wating for Extension Release" in the search for the release note I also get non-default plugins.
How was this intended to be working?
I see that this new state will be an invitation to total confusion.
Waiting For Release
means - put in next release note!
means closed. After a TWiki release all the Waiting For Release goes in Closed.
Bugs that are raised on code that was introduced AFTER the last release are also going to Closed because there is no point in telling upgraders that a bug was introduced and fixed between two releases.
We should maybe right after next release of TWiki change the bugs web so it gets a "Flag For Release Note" field instead and then let all bugs go in closed and use the Waiting For Release state as Arthur intended with the Waiting For Extension Release.
I reverted the change and updated the 5 items that had all used it wrong so far.
- 12 May 2007
I'll back you on that; the bugs form is already fairly complex, and I'd rather not have any more fields. On the flip side, extensions do
need their own lifecycle. IMHO the release notes for the default TWikiFor
should be built on the basis of looking up the engine and the set of extensions that are identified as belonging to the standard TWikiFor
, but that shouldn't stop extension authors from using Waiting for Release in their own way. Waiting for Release on an extension, BTW, means it is in subversion, but not yet uploaded to t.o.
- 12 May 2007