• Do not register here on develop.twiki.org, login with your twiki.org account.
• Use View topic Item7848 for generic doc work for TWiki-6.1.1. Use View topic Item7851 for doc work on extensions that are not part of a release. More... Close
• Anything you create or change in standard webs (Main, TWiki, Sandbox etc) will be automatically reverted on every SVN update.
Does this site look broken?. Use the LitterTray web for test cases.

Item4052: Waiting for Extension Release breaks release notes (Developers read this)

Item Form Data

AppliesTo: Component: Priority: CurrentState: WaitingFor: TargetRelease ReleasedIn
NotTWiki Bugs Normal Closed   n/a  

Edit Form Data

Reported By:
Applies To:
Current State:
Waiting For:
Target Release:
Released In:


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!

Closed 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.

-- TWiki:Main/KennethLavrsen - 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.

-- TWiki:Main.CrawfordCurrie - 12 May 2007

Summary Waiting for Extension Release breaks release notes (Developers read this)
ReportedBy TWiki:Main.KennethLavrsen

SVN Range TWiki-4.1.2, Fri, 11 May 2007, build 13693
AppliesTo NotTWiki
Component Bugs
Priority Normal
CurrentState Closed


TargetRelease n/a

Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View |  Raw edit | More topic actions
Topic revision: r2 - 2007-05-12 - TWikiUserMapping_CrawfordCurrie
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback