User Tools

Site Tools


bacnet:project_management:btl_wg

Differences

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

Link to this comparison view

Next revision
Previous revision
bacnet:project_management:btl_wg [2012/05/08 17:16] – created desolatbacnet:project_management:btl_wg [2019/12/18 16:00] (current) – ↷ Page moved from tools:bacnet:project_management:btl_wg to bacnet:project_management:btl_wg desolat
Line 19: Line 19:
   * Implementation Guidelines   * Implementation Guidelines
  
 +===== Issue Management =====
 +  * {{:bacnet:lori_btl_workflow_documents.pdf|Lori's BTL workflow idea}}
 +    * "Internal Task List" and "Running Change List" can be represented by "Version" and "Milestone" fields of an ITS
 +    * documents can be referenced in corresponding issues is a seperate field (hyperlink to document storage (SVN, GoogleDocs, ...)
 +    * :?: Why should addenda be necessary? Why not collect changes (addenda, errata) into a minor version Test Package (e.g. 9.1, ...), which is released regularly?
 +    * "Summary of changes" could be all resolved issues with a certain Milestone 
 +  * :!: BTL-WG Meeting Minutes 2011-11-14 2c: efficiency improvement discussion
 +
 +===== Analysis =====
 +  * Why are not all files on the FTP?
 +    * most current work item files
 +      * e.g. wID0044
 +    * most current draft test plan and test definitions
 +      * e.g. TP9.0c-5
 +  * Where can one find out what work items made it into which test package version?
 +    * work-to-do: ACCEPTED and "TestPkg Rev"
 +  * Why do we not keep the most current work-to-do in one place on the FTP?
bacnet/project_management/btl_wg.1336490188.txt.gz · Last modified: (external edit)