Release Feature Table
This topic is for including in Release topics (CairoRelease, DakarRelease, EdinburghRelease) to display the Features, Bugs etc. scheduled for the release.Usage
To include it in a topic use the following lines:
<!--
* Set RELEASETABLE = %INCLUDINGTOPIC%
-->
%INCLUDE{"ReleaseFeatureTable"}%
The RELEASETABLE variable is used instead of just using
%INCLUDINGTOPIC% so that the tables can be altered in this topic without having to refer to another topic to view the affect.
To test it in this topic on different releases set the following RELEASETABLE variable:
- Set RELEASETABLE = Release
Features Scheduled for Codev.Release
Search for non-bug topics marked as Scheduled for Release:
Bug Fixes Scheduled for Codev.Release
Search for Bug topics marked as Scheduled for Release: ReleaseSummary and ReleaseUpgradeGuide
"Nice to Have" List
Search for unsponsored (AssignedToCore not set) features marked as Scheduled for Release:| Item | Type | Developer | Spec | Impl | Docu |
|---|---|---|---|---|---|
| SlimDownFatCgiScripts | FeatureDone | 50% | 0% | 0% | |
| Total: 1 |
-- SamHasler - 25 Jul 2004
Update History
CrawfordCurrie said in CairoReleaseSummary: "I wasn't sure why all the features and enhancements added in "patches and other stuff" were relegated to the bottom of the pile, so I merged them with *Features and Enhancements*" I think it was just following the format of the tables in CairoRelease. I added the patch section as there searches didn't find all topics scheduled for a release. There wasn't any logical reason for it so I've updated this topic to only have two sections. In looking at this I've also discovered that DocRequest topics were falling through the cracks. Luckily there were none scheduled for Cairo, and 2 for Dakar. I've updated both sets of tables to simply search for TopicClassifications of Bug.* and not Bug.* so nothing should slip through now and it will make the topics load faster. -- SamHasler - 20 Aug 2004 I've changed the totals calculations from$INT($AVERAGE($ABOVE())) to $INT($EVAL($SUM($ABOVE())/$ROW(-2))) because $AVERAVE wasn't counting the blank fields.
-- SamHasler - 20 Aug 2004
I've the tables to put anything without AssignedToCore in the a nice to have table so that they can be automated. It seems pretty logical from reading ScheduledFor and AssignedToCore.
-- SamHasler - 07 Sep 2004
Removed progress and gauges from "Nice to Have" table as they don't provide meaningful numbers, slow down topic views and it makes the tables easier to distinguish.
-- SamHasler - 10 Sep 2004
Feedback
Is there any way to allow the summary gauges for the above tables to be "included" at the top of the topic as well as with their respective tables? -- GrantBow - 02 Feb 2003 The gauges in the tables have a double quote after them when they are included. I was thinking it's better to just switch them over and sort the cosmetic bug out later. I remember it happened before on CairoRelease although that wasn't with the include. I'm guessing the include is somehow re-triggering it. -- SamHasler - 28 Jul 2004 Note to self I'd like to put the topic summary in title tags to the links so that you can hover over the topic names to see it in a popup but I don't want to do it until performance improves. -- SamHasler - 07 Sep 2004 Just noticed that the gauges don't show the correct values. Probably related to the quote problem mentioned above. Note The original gauge problem was caused by PluginExecutionOrderBroken. I'm guessing the include is changing the execution order in some way. -- SamHasler - 10 Sep 2004 Hmm, this is still showing some topics assigned to Dakar on the old form, they need to be upgraded to ChangeProposalForm. -- SamHasler - 28 Apr 2006
Site map
Blog web
Create New Topic
Index
Search
Advanced search
My topics of interest
Changes
Major changes only
All tags
Notifications
RSS Feed
Statistics
Preferences
Community 
Readme first
Developers News
How you can help
Community roles
#twiki IRC
Lima Release
Feature Proposals
Bugs Changes
Categories 
Account 
Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.Copyright © 1999-2026 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.