2014年5月14日 星期三

Redmine - Implementation


  • System installation
    • Basic installation
      • standard installation
        • Ubuntu Linux(or  MS Windows)
        • Apache
        • MySQL (or Postgre SQL)
        • Redmine
        • Ruby & Rails
      • bitnami installation
        • packed installer
        • Virtual Machine (*)
          • VMWare and VirtualBox are all workable.
    • Email setup
      • Modify configuration.yml under /opt/bitnami/apps/redmine/htdocs/config
      • Fill up the SMTP information (our SMTP server or Email)
    • Subversion integration
      • Link the exist repository
      • Link between Revision and Issue
        • Standard link
          • Go to specified revision under Repository page
          • Add the Issue id releated.
        • Subversion message log
          • #XXX will be translated to a link refer to the Issud ID XXX
        • Issue comment log
          • rXXX will be translated to a link refer to the Revision ID XXX.
    • System backup/restore
      • Backup items
        • Redmine database
          • For MySQL:
            • mysqldump -u root -p XXX bitnami_redmine > sqldump.sql
        • Attached files
          • rsync -a /opt/bitnami/apps/redmine/htdocs/files /mnt/storage/redmine/files

  • Work Flow
    • Issue reporting flow
      • Bug fix flow
        • Reporter creates an issue with “New” state and assign to TaskOwner
        • TaskOwner assigns the issue to the Developer (TaskOwner may be the issue owner). 
        • Developer changes the state to “In Progress” when handling.  
        • Developer changes the state to “Resolved” or “Rejected” then assigned to Verifier
          • Resolved: Solution provided for verification. 
            • Verifier changes the state to “Closed” and changes the assignee to NULL if the solution has been verified. 
            • Verifier changes the state to “ReOpen” and assign back to Developer if the solution is not workable. 
          •  Rejected: Invalid testing procedure or Work As Design issue. 
            • Verifier changes the assignee to NULL if he/she agree with that. 
            • Verifier changes the state to “ReOpen” and assign back to Developer if the Rejected” reason if not acceptable.
        • Reporter/Verifier has right to change state from “Closed” to “ReOpen” and assign to Developer if the same issue happens again.
    • Project management of a development flow
      • TaskOwner Creates ToDo list
        • Creates issues with "Feature" category
        • Setting constraints between issues.
        • Fills up the estimated start/end date and working hours of the issue
        • Checks the Gantt Chart 
      • TaskOwner Create Roadmap
        • Create Versions and assign feature issues to specified Version 
      • Team work (TaskOwner)
        • Assign specified issue to Developer
        • Update the start/end date of the issue and related issues.
        • Checks the Gantt Chart.

沒有留言:

張貼留言