You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 7, 2024. It is now read-only.
Hi!
I'm currently digging through all the bolt dependencies to package it for Arch Linux. I noticed that bolt depends on puppetfile-resolver. Given that bolt is stable and relies on puppetfile-resolver and a stable API, it can be considered stable and get a 1.0 release?
Also: Is it planned to migrate the project to the Puppetlabs namespace? In the past it was quite tricky to move forward with rspec-puppet/puppet-lint because it's tightly integrated into the puppet ecosystem, but hosted in a personal namespace and the maintainer abandoned it. It would be nice if such situations could be avoided in the future.
The text was updated successfully, but these errors were encountered:
Heya @logicminds . I have no plans for it. I've stepped away from a lot of Puppet stuff. Happy for people to fork, or if you really way, migrate to a different namespace.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi!
I'm currently digging through all the bolt dependencies to package it for Arch Linux. I noticed that bolt depends on puppetfile-resolver. Given that bolt is stable and relies on puppetfile-resolver and a stable API, it can be considered stable and get a 1.0 release?
Also: Is it planned to migrate the project to the Puppetlabs namespace? In the past it was quite tricky to move forward with rspec-puppet/puppet-lint because it's tightly integrated into the puppet ecosystem, but hosted in a personal namespace and the maintainer abandoned it. It would be nice if such situations could be avoided in the future.
The text was updated successfully, but these errors were encountered: