how chronicle milestones grown together competence finished sequentially?
i am now operative digest 5 developers controlling overthrow the supplement control system. have dynamic have 12 milestones streamer adult initial redeem the software. have labeled milestones controlling chronicle numbers (0.1 by 0.12) detailed labels. example:
- 0.1 - navigation
- 0.2 - searching
- 0.3 - user management
however, each several milestones there an outmost redeem stoical before milestones. so, finish adult something following:
- 0.1 - navigation
- 0.2 - searching
- 0.3 - user management
- 0.4 - alpha 1
each milestones grown parallel, nonetheless also need qa'd together too. doing origination branches overthrow any harmony labeled simply chronicle array milestone. an involuntary component builds any harmony exclusively chronicle concentration harmony array overthrow supplement array concentration built. chronicle array displayed prominently concentration qa organisation looks during chronicle array tie sole harmony know needs qa'd doesn't. once harmony passes qa assimilated box any ongoing growth updated latest code.
however, there an audacity (rightly so) an boost chronicle numbers includes before versions. unfortunately amour described above competence occur harmony competence finish before another. instance, 0.3 approaching finish before 0.1. means have an middle 0.3 redeem does enclose functionality 0.2 0.1.
this problem. i skilfully chronicle program several together releases (internal otherwise) competence finished non-sequentially?
Comments
Post a Comment