Once tickets have been reviewed and approved by the Development Prioritization sub-team, they become available to be worked on by developers and are added to the prioritized backlog. The Program Team regularly reviews prioritized tickets to match them with available development resources. Just like many of the archives we serve, we have a substantial backlog due to the size of the community and the relative level of demand for ArchivesSpace compared to the finite resources of a relatively small non-profit organization. When a compelling case can be made that there will be funds available to do more without harming ArchivesSpace’s long-term sustainability, the Program Team works with the ArchivesSpace Governance Board to get additional resources, such as with the recent addition of a full-time Front End Developer to the team.
...
You may notice that there are times that lower priority tickets get worked on sooner than higher priority ones, and that an ArchivesSpace release may contain a larger number of tickets you consider lower priority compared to a feature you’ve been anxiously awaiting. This is because there are more possibilities for development solutions addressing these kinds of tickets. (If it helps, think of this as similar to making decisions about who can work on what in your archives successfully, and why certain piles get worked down more quickly than others.)
The roadmap, which is informed by knowledge taking a long view of overall priorities through past surveys and formal and informal community discussions and distributed to the community, serves as the guidepost for determining larger projects to work on. It is usually the basis for creating sprints of issues from the prioritized backlog. The program team aims to update the roadmap after each release and when there a are major changes due to unexpected changes in staffing or outside conditions.
...