Archivematica Roadmap - archivematica/Issues GitHub Wiki

About the roadmap

We utilise the Now-Next-Later format to express our current and future work on Archivematica and its dependencies. This allows us to communicate our work openly, while maintaining flexibility and the ability to make new discoveries to support the project. Rather than being time bound, we acknowledge the complexity of software development and the need to be innovative and product led.

The Now category acknowledges the release and other high priority work we are currently undertaking. This work is viable and clearly defined. Some of this work might be project-related, but not for the next release. We use milestones to group issues together for the current release. Viewing a milestone will give you all the issues being addressed, even if they are not expressed in this roadmap. Milestones will always have the most up-to-date release information. If an issue is not tagged to a milestone then it is not going to be included in the release.

The Next section of the roadmap articulates the upcoming problems being scoped and is always dependent on the outcomes of current work. This can include reprioritised work. There is always space to add to it as we move it to the Now category.

The Later work characterises our long-term goals for Archivematica. They are things we would like to tackle, but the research to better understand the problem has not been done. Sometimes the work in Later is broad in scope, ready to be broken into smaller, viable tasks. There is no time limit to things residing in the Later category.

Archivematica Roadmap

Updated: 24 July 2025

Now

Next

  • 1.19 release planning
  • Django upgrade
  • Reviewing potential FPR rules and general management of FPR
  • Investigation on containerised deployments with Docker

Later

  • Further dependency review and updates
  • Investigation of VeraPDF as validation tool