The public roadmap for Tower is a place to share upcoming product features and priorities to help our users and customers plan ahead.
It contains current and future developments and allows Tower Cloud customers to provide feedback. The public roadmap outlines the most important upcoming features – it doesn't include most contributions from volunteers outside the company. It is not intended as an authoritative list of upcoming release notes.
Q: Why did you build this?
A: We know that our customers are making decisions and plans based on Tower development. We want to provide users and customers with the insights they need to plan.
Q: Why are there no dates on your roadmap?
A: Our priority is security and operational stability. Due to this, we can't provide specific target dates for features. The roadmap is subject to change at any time, and roadmap issues in this repository do not guarantee a feature will launch as proposed.
Q: What do the roadmap categories mean?
- Shipped: Included in the latest enterprise release.
- Coming soon: Feature is available for beta preview for selected customers
- We're working on it: Development work is ongoing; the feature is taking shape.
- Discovery and design: We are working through the implementation details or scoping the feature out.
- Ideas: We are assessing the ideas and thinking through how it might work. This is the best phase to share your feedback on how you want to see something implemented. Use cases and design ideas are more than welcome here.
Q: Is everything on the roadmap?
A: Many of the milestones are included in the public roadmap. We do not include most development work focused on the inner workings of the application.
Q: How can I provide feedback or ask for more information?
A: The preferred way for Seqera customers to reach out is via the dedicated support channels. Comments are also enabled in the public roadmap.
Q: How can I request a feature be added to the roadmap?
A: The preferred way for Seqera customers is to make a feature request in the dedicated support channels. Alternatively, create an issue in the Tower community version repository.