User Tools

  • Logged in as: anonymous (anonymous)
  • Log Out

Site Tools


mantisbt:roadmap_requirements

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
mantisbt:roadmap_requirements [2008/05/19 16:17] – feedback SneakyWho_am_imantisbt:roadmap_requirements [2011/11/16 07:29] (current) – The page rendering was broken (maybe since new PHP version on mantisbt.org). Added new line to fix it at end of file. atrol
Line 66: Line 66:
      * **(Done)** Issues done (i.e. 20 issues resolved out of 30 planned).      * **(Done)** Issues done (i.e. 20 issues resolved out of 30 planned).
      * **(Done)** Release description (if not empty).      * **(Done)** Release description (if not empty).
 +
  
  
Line 80: Line 81:
  
   * Why does there has to be an additional field that becomes obsolete after the bug is resolved (and the value is copied into "fixed in version"? We renamed "fixed in version" to "target version", use it for both purposes and are quite happy with it. (polzin)   * Why does there has to be an additional field that becomes obsolete after the bug is resolved (and the value is copied into "fixed in version"? We renamed "fixed in version" to "target version", use it for both purposes and are quite happy with it. (polzin)
-          --   * That sounds like a good idea. I will be keeping both values though. It is clutter but I like it how it is. One box is for what SHOULD happen, and the other is for what DOES happen. So for me, at least, it is a way to see if we are meeting our goals. My main problem is with the wiki page itself. It could probably use redoing to some extent (for example, database changes? The method for adding the field to the reporting screen is no longer really applicable...)~~~~+             * That sounds like a good idea. I will be keeping both values though. It is clutter but I like it how it is. One box is for what SHOULD happen, and the other is for what DOES happen. So for me, at least, it is a way to see if we are meeting our goals. My main problem is with the wiki page itself. It could probably use redoing to some extent (for example, database changes? The method for adding the field to the reporting screen is no longer really applicable...) (SneakyWho_am_i)
  
   * maybe also add a field to set a version as "private/public" to add milestones/planned releases for developers, without showing them publicly yet (rolf)   * maybe also add a field to set a version as "private/public" to add milestones/planned releases for developers, without showing them publicly yet (rolf)
  
   * adding an optional target_date to the version table seems redundant. Using the current date_order field allows for all the flexibility required to implement version due dates. To implement due dates at the version level use the date_order field as the target date until a version is released. Then display the date next to the version title in the roadmap. If the current date exceeds the date_order field and the version is not released have the roadmap page highlight the projected released date in red or some other color to show the due date has passed. If wanted it would be trivial to add the number of days the version is late by appending a negative number to the end of the due date. (herringm)   * adding an optional target_date to the version table seems redundant. Using the current date_order field allows for all the flexibility required to implement version due dates. To implement due dates at the version level use the date_order field as the target date until a version is released. Then display the date next to the version title in the roadmap. If the current date exceeds the date_order field and the version is not released have the roadmap page highlight the projected released date in red or some other color to show the due date has passed. If wanted it would be trivial to add the number of days the version is late by appending a negative number to the end of the due date. (herringm)
 +
mantisbt/roadmap_requirements.1211228262.txt.gz · Last modified: 2008/10/29 04:31 (external edit)

Driven by DokuWiki