Wrong release boundaries for project trove
Bug #1203190 reported by
Ilya Shakhat
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Stackalytics |
Fix Released
|
High
|
Ilya Shakhat | ||
Bug Description
The proposed boundary for Havana release should be b8e274685daaf6d
| Changed in stackalytics: | |
| importance: | Undecided → High |
| status: | New → Triaged |
| milestone: | none → 0.1 |
| Changed in stackalytics: | |
| milestone: | 0.1 → none |
| Changed in stackalytics: | |
| milestone: | none → 0.2 |
Revision history for this message
| Ilya Shakhat (shakhat) wrote | #1 |
| Changed in stackalytics: | |
| assignee: | nobody → Ilya Shakhat (shakhat) |
| status: | Triaged → Fix Committed |
| Changed in stackalytics: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Release cycle of Trove is not aligned with the core cycle, releases will be matched by dates. Such matching is implemented in blueprint auto-assign-release