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.
2024We’ve got some big plans! In addition to implementing some new feed types, we’re going to put a lot of work into improving our Software Composition Analysis (SCA) features: vulnerability scanning, licensing scanning, projects, etc.
2024Integrations, integrations, integrations! In particular, cloud deployment targets and a better Helm/Kubernetes integration. There’s definitely some areas of improvement on the UI as well.
2024There’s a lot that we intend to bring over from BuildMaster, but we’re seeing opportunities to improve “Otter as a script runner” – and think there’s definite improvements we can make there.
SCA
&
Security
& Compliance
2023This release saw a lot of back-end work, namely “centralizing” package information in the database. We also continued to focus on Software Composition Analysis (SCA), including making some vulnerability scanning improvements (including our own database). We also added a lot of “smaller” changes, including improving NuGet Symbol Support, a Web-based Universal Package Editor, and a better feed-creation experience. Last but not least, we improved SSL support and Active Directory integration.
2023We are focusing on making CI/CD easier to configure by adding more integrations and script templates; this includes first-class Docker integration (for both “containerized builds” and CI/CD for your own containers), first-class npm support, first-class support for Cloud-deployment targets, etc. We also totally redid the Issue Tracking integration. We will also improve SSL support and Active Directory integration.
2023We made a number of UI tweaks, including the ability to clone job templates and navigate a bit easier. We also brought library, SSL support, and Active Directory integration changes from our others products.
Integrations
&
User-experience
2022With 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!
2022We’ve revamped the BuildMaster user experience, namely around creating new projects/applications, and included Git-browsing and Script templaes.
2022We introduced Software Composition Analysis (SCA) features, including Software Bill of Materials (SBOM) generation and repository. There will also be a big improvement of the replication user experience, as well as the introduction of ProGet Edge Computing Edition to help with content (packages, container images, assets) from hub to edge servers.
Platform Updates for a Unified Codebase (.NET6)
&
User-experience Focus
3.0This 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.
7.0This 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.
6.0We 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.
Fully Container-ized
&
Self-service Improve-ments
5.3This 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.
2.3It 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.
6.2First-class support for Packages and Containers, Git-based configuration with rafts, and template-based applications.
General Platform Updates
&
Initial Container Support
5.2Features 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.
2.2Improved Git integration, performance, and scalability.
6.1-R2Side-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
5.1Expands 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.
2.1Applies the concepts of CI/CD to infrastructure management by supporting pipelines for infrastructure-as-code development and deployment.
6.1Returns 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
5.0
2.0
6.0
Updated UI
&
new logos
Self-managed DevOps Tool
Inedo HQ
56 Front St. Upper
Berea, OH 44017 United States
Inedo Japan
3-20-1 Daiwa Azabu Terrace 5F, Minami-Azabu
Minato-Ku, Tokyo 106-0047
