At Inedo, we don’t force our customers to be guinea pigs that test a stream of never-ending, never-quite-complete features. That doesn’t mean we don’t innovate – in fact, we continually strive to improve our products through not only our own vision, but also through user feedback. To accomplish this, we have two categories of releases.
A major release typically implements a brand new feature or overhauls an existing one, and likely contains backwards-incompatible API changes.
1 major release per product per year
A maintenance release may contain backwards-compatible enhancements, bug fixes, and security patches.
2 maintenance releases per product per month
Our roadmap reflects what we’ve done, and what we plan to do.
With success as a PowerShell script runner, we’ve added more scripting languages (Python, Batch, etc.), as well as a brand-new OtterScript editor. There’s also a new licensing model!
We’ve got big plans for simplifying the BuildMaster user experience, namely around creating new projects/applications.
The major change we’re planning is an improvement of the replication user experience, as well as introducing a new “edition” of ProGet to help with content (packages, container images, assets) from hub to edge servers.
Platform Updates for a Unified Codebase (.NET6)
This was a transformative release that re-envisioned Otter as a tool that helps with “compliance as code”, in addition to declarative configuration. Self-service automation through Job Templates is also a major improvement. We plan to continue UI improvements through maintenance releases.
This was mostly a platform update to .NET5, which enabled run on Linux as a container. There were also big improvements to Release Templates to help make self-service automation easier.
We added a lot of features to make ProGet easier to manage, including Simplified API Key Management, Automatic Vulnerability Assessment, Feed Groups, and Lots of other End-User Experience Improvements. We also made some big changes to Asset Directories.
This is a transformative release that focuses on containers, and brings our container features on-par with package features: semantic versioning, layer visibility, etc. But there is also be some great improvements for packages as well: you can see where your packages and containers are actually being used, not just where they’ve been deployed in the past.
It was a crazy year, to say the least. We decided to just combine the platform updates planned for 2.3 into the product updates for 3.0.
First-class support for Packages and Containers, Git-based configuration with rafts, and template-based applications.
General Platform Updates
Initial Container Support
Features new feed types for Python (PyPI), Debian, and Helm, along with a Feed Management API that allows feeds, connectors, and more to be configured through a new REST API.
Improved Git integration, performance, and scalability.
Side-by-side implementation of 6.2’s features with a vision for long-term stability for 6.1.
Inedo Hub pre-release access
expanded third-party integration
Expands on the protocol for Universal Packages with virtual package support, used to bundle packages together and allow packages to reference large assets instead of containing them directly.
Applies the concepts of CI/CD to infrastructure management by supporting pipelines for infrastructure-as-code development and deployment.
Returns BuildMaster to its namesake as the definitive source of truth for all your builds and releases, adding source control repository monitors & GitHub/GitLab hooks, while reintroducing unit testing & build reports.
Inedo Hub, Continuous Integration & Continuous Delivery