Roadmap

[luishdez]

A basic initial roadmap

• Setup travis
• Update README.md regarding the fork and travis badge ( follow apache 2.0 LICENSE )
• Fix travis build for ruby 1.9.3 Fix compatibility with ruby 1.9.3 #34 in order to have CI
• Update metadata.rb and submit to market. Which name should we use? Discussion: Naming convention for supermarket meta#3
• Review and tag pending pull requests
• Define an strategy to clean PRs
• Merge/Clean easy PRs
• Support for MongoDB >3.0 Branch: https://github.com/chef-brigade/mongodb-cookbook/tree/mongodb-v3

[luishdez]

@josephholsten, I need your approval in order to setup travis. I did a request to grant access. Though I guess you can setup travis easily as you are the original owner of the organization.

Anyways I hope that the original repo can be transferred ...

[josephholsten]

Travis setup: approved!

[luishdez]

Ok, I've been reviewing a little bit all pending PRs, tagged some…

There are a few very complex PRs for core features like sharding/replicaset that are very distant in time "some of them from 2013"… Those are PRs to the master branch and they conflict with each other. Merging that is too complex.

Check these PRs: https://github.com/chef-brigade/mongodb-cookbook/labels/comp%3A%20replicaset

A possible strategy would be:

1. Locate, tag and merge easy PRs for quick fixes. Like basic features, bugs, and compatibilities. These PRs are easy to merge right now.
2. Drop the complex PRs and work in a new branch for each "main" feature by order.
   1. LWRP
   2. Replicaset/sharding
   3. User management
   4. Backup management … mms etc.

The idea is not to drop all the code from PRs but taking the initial ideas or pieces that we can use. IMHO Working in a clean slate is going to be much easy.

[damacus]

I think this is a good start for the 1.0.0 rewrite. @shortdudey123 will probably write another set of issues in the bug track for it if we've missed anything!

Please see the milestone for progress https://github.com/sous-chefs/mongodb/milestone/2

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.