Skip to content
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

Closed
5 tasks done
nanliu opened this issue May 27, 2015 · 11 comments
Closed
5 tasks done

0.5.0 Roadmap #62

nanliu opened this issue May 27, 2015 · 11 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@nanliu
Copy link
Contributor

nanliu commented May 27, 2015

#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.

@nanliu nanliu added the enhancement New feature or request label May 27, 2015
@nanliu nanliu added this to the 0.4.0 milestone May 27, 2015
@nibalizer
Copy link
Member

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.

@nanliu
Copy link
Contributor Author

nanliu commented May 27, 2015

Travis is sufficient for now, do we have a standard gemfile/.travis.yml config for puppet-community?

@nibalizer
Copy link
Member

https://github.com/puppet-community/puppet-extlib has a good Gemfile, Rakefile, .travis.yml
That also provides hooks for you to setup blacksmith deploys of archive. I'm not sure if you want to keep publishing this to your own namespace or use forge.puppetlabs.com/puppet.

The secure: line comes from:
https://github.com/puppet-community/plumbing/blob/master/share/travis_secrets

@jairojunior
Copy link

@nanliu can you publish a 0.3.1 version in forge with archive::nexus support?

@nibalizer
Copy link
Member

#64 would enable the bits to enable push button deploys, which would open the door to a 3.1

@MartinMeinhold
Copy link

@nanliu can you publish a 0.3.1 version in forge with archive::nexus support?

+1

@logicminds
Copy link
Contributor

+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.

@jyaworski
Copy link
Member

#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.

@jyaworski
Copy link
Member

Also, @nanliu should this issue be for 0.5.0 now?

@nanliu nanliu changed the title 0.4.0 Roadmap 0.5.0 Roadmap Feb 29, 2016
@nanliu
Copy link
Contributor Author

nanliu commented Mar 1, 2016

@jyaworski, issue updated, looking for volunteers to test:

@nanliu nanliu modified the milestones: 0.5.0, 0.4.0 Mar 1, 2016
@nanliu nanliu self-assigned this Mar 1, 2016
@jyaworski
Copy link
Member

Merged #124

@nanliu nanliu closed this as completed Mar 11, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

6 participants