74c236ac38
It is easy to oversubscribe ourselves during a release cycle. We approve specs only to experience that we fail to review consistently; code is posted last minute, we get lost into chasing race conditions, the odd dependency throws the gate under the bus, and the ever-present cosmetic refactoring patch steers our attention from what matters, which is *reviewing what we commit to deliver*. In order to keep ourselves focused on the bigger picture, this patch proposes/formalizes changes to the way we register blueprints so that we can improve our ability to better foresee what we'll deliver at the end of a release. We obviously can't predict the future or chain people to a desk, but a regular pulse check of a well planned task list should at least help mitigate the feeding frenzy that usually happens closer to FF. That inevitably leads to half-baked and buggy solutions. Change-Id: Ia27b2a779204bf98c1dec2a30d00507de285f801 |
||
|---|---|---|
| .. | ||
| source | ||
| Makefile | ||
| pom.xml | ||