ProGet Roadmap

ProGet is by no means "feature complete". Although the software works great for our users today, we're actively working on making it even better.

To give you an idea of where ProGet has been, and where we see it going, we've put together this roadmap page. It's a bit rough, but it should show you which changes we plan on making in releases to come.

We decide on what changes to make to ProGet based on a number of factors, the largest of which is user features requests. If there's anything you think ProGet should do — or should do better — please contact us and let us know.

Version 4

The central theme of v4 is all about universal package management, which means managing all of the various types of packages and feeds in the enterprise.

Whitesource Integration

  • License Filtering and Vulnerability Scanning Extension
  • This will be delivered as an extension for ProGet 4.7 or later.

Assets

  • It's important to always use the right tool for the right job. Packages, such as ProGet's Universal Packages, which are great tools for storing self-contained versioned artifacts, complete with rich metadata, and dependency information. However, not everything is a package, and sometimes a file is just a file. ProGet Assets allow arbitrary file storage with easy access via web browser and a RESTful API.
  • This is currently in draft specification, and is scheduled for ProGet 4.8.

Improved Active Directory / LDAP

  • Organizations with complex, mutli-domain active directory structures often have challenges using our current active directory implementation. We are working on completely rewriting it, along with allowing a fallback option in case loading the extension fails.
  • This is currently available or BuildMaster has a beta extension, please contact us for testing it. Given the complexity and variance in each organization, your assistance in testing is always appreciated (even if you're not using BuildMaster).

Containers

  • Although we don't believe that containers are the future for all software across all organizations, they will continue to play in important role in many organizations' application architectures. We are committed to providing tools that enable simple yet powerful workflows for working with containers
  • ProGet will serve as the repository for container images you build in house, as well as third-party images you want to manage

Cloud / PaaS

  • Applications "built for the cloud" (i.e. using a PaaS or "serverless" approach) will be another alternative for organizations.
  • ProGet will host the packaged application components that are deployed to the various datacenters

PowerShell and DSC

  • PowerShell is the standard for automating configuration on Windows servers, and while we've certainly embraced it's use throughout BuildMaster, Otter, and ProGet, there's still some room to improve, especially when it comes to PowerShell DSC.
  • We would love to see BuildMaster and Otter users be able to use ProGet to host DSC resources, and easily create DSC-based plans from the visual editor.

We don't exactly have a schedule for these, but if you're interested in seeing them sooner, let us know.

  • New Service Messenger
  • New Inedo Agent
  • Resource Credentials
  • Read Git Repositories
  • Composer Feed

Already Released

  • ProGet 4.0 - Updated UI, Universal Feeds & Packages
  • ProGet 4.1 - PowerShellGet support, multi-site replication across ProGet instances
  • ProGet 4.2 - CDN/Cloud (S3, Azure) Package Storage
  • ProGet 4.3 - Docker repository support, SDK improvements
  • ProGet 4.4 - Package promotion, deployment records, and Linux
  • ProGet 4.5 - Support for RubyGem repository
  • ProGet 4.6 - Vulnerability Scanning
  • ProGet 4.7 - License Filtering, Support for Visual Studio Extensions (.vsix)

Version 3

The central theme of Version 3 was to extend the reach of package serving to other registries/repositories including npm.

v3 is partially supported, which means that we will provide technical assistance to v3 users who have not yet upgraded, and will assist in upgrades. However, we will no longer ship maintenance releases, patches, or other changes.

Version 2

Version 2 of ProGet introduced more filtering options (particularly for license types), and added meta-features such as the SDK, the API, and source code licensing. We also decided to make the symbol & source server available in the free edition.

v2 has been retired and is no longer supported.

Version 1

The initial release of ProGet provided basic NuGet feed support while introducing features such as connectors, filtering, multiple feeds, along with an integrated symbol & source server for NuGet packages.

v1 has been retired and is no longer supported.