-
-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.5.0 Roadmap #62
Comments
This is pretty sweet. I'm excited to see open development and roadmap. Are there any testing needs you have that travis can't provide? That's kindof my current kick. @igalic mentioned that we may be hitting max_concurrent travis testing now. |
Travis is sufficient for now, do we have a standard gemfile/.travis.yml config for puppet-community? |
https://github.com/puppet-community/puppet-extlib has a good Gemfile, Rakefile, .travis.yml The secure: line comes from: |
@nanliu can you publish a 0.3.1 version in forge with archive::nexus support? |
#64 would enable the bits to enable push button deploys, which would open the door to a 3.1 |
+1 |
+1 for not having to install faraday on every system, especially when no internet access is available or a local ruby gems server. I have been working on a hacked version that bundles the gems inside the files directory. |
#82 brought us up to date with https://github.com/puppet-community/modulesync_config so we're in line with some other modules and their styling/methodology. |
Also, @nanliu should this issue be for 0.5.0 now? |
@jyaworski, issue updated, looking for volunteers to test:
|
Merged #124 |
#55 identified a memory usage problem for archive module. Our goal for 0.5.0 is to resolve this problem and address the following issue.
Since this requires several changes, master will be unstable until we resolve them. Please feel free to discuss or comment on this issue if you have any input.
The text was updated successfully, but these errors were encountered: