[SERVER-5747] What do Planning Bucket A and Planning Bucket B mean? Created: 02/May/12 Updated: 02/May/12 Resolved: 02/May/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Nathan Wells | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
This really has nothing to do with MongoDB, but rather a process question... What do the various versions below mean, and does the order below represent the "planned" order of implementation? I'm not looking for guarantees, but rather want to make sure that my expectations are in line with how you're using JIRA.
|
| Comments |
| Comment by Nathan Wells [ 02/May/12 ] |
|
Thanks! |
| Comment by Andy Schwerin [ 02/May/12 ] |
|
The buckets act as an attempt to roughly order tickets, without respect to particular release versions. We generally expect to do stuff in A before B before "not scheduled", at the time that we put it into the bucket. However, anything from any of these buckets may get pinned to a specific release out of order. |