Roadmap

0.3.0

about 21 months late (05/27/2010)

puppet-module 0.3.0

0%

0 closed (0%)   6 open (100%)

Related issues
Bug #12249: Forge needs search to support substring matching description, name and exact match on keywords
Bug #12374: We should validate dependencies and prevent dependency issues on upload
Bug #12408: Cleanup dependency data for current modules
Feature #12257: Forge API needs to provide necessary dependency data to make constraint resolution possible on install
Feature #12264: Selenium tests for the forge should be written and run on CI
Feature #12423: Forge should validate uploaded modules version range declarations

0.2

57%

4 closed (57%)   3 open (43%)

Related issues
Bug #3595: Documentation should explain the "Modulefile" Ruby DSL and "metadata.json" formats
Bug #3614: Site's routes should not collide
Bug #3742: Site's login should be secured with SSL
Bug #4128: Site's stylesheets should not cause panic or nausea
Bug #4718: Site's tagging library should allow initial migrations to run
Bug #12171: Forge should grab version out of git tag
Feature #3892: Site should support Open ID authentication

0.2.1

20%

1 closed (20%)   4 open (80%)

Related issues
Bug #4132: Module package contents should match the class name
Feature #3897: Site should make it easy to find the puppet-module tool
Feature #4699: Site should have a page that displays all tags and navigation that links to it
Feature #4700: Site's tag cloud should only show popular tags
Refactor #4611: Site's tags should be manually consolidated

0.2.2

0%

0 closed (0%)   1 open (100%)

Related issues
Bug #4118: Site should specify lengths and validations for all string columns in database

0.2.3

0%

0 closed (0%)   2 open (100%)

Related issues
Bug #4088: dependency parsing issue with modules that have a dash in the name
Bug #4701: Site's tag input field should help user tag items using autocompletion

0.3

0%

0 closed (0%)   2 open (100%)

Related issues
Feature #3814: Site should list number of downloads for modules
Feature #3896: Site homepage should show most recent/popular modules

0.3.2

25%

1 closed (25%)   3 open (75%)

Related issues
Bug #3619: Tool should validate module metadata before using it and provide helpful error messages
Bug #3882: Tool should display clearer error message when trying to build a module without a Modulefile
Bug #3954: Tool should use the module name as the directory name and "name" metadata field
Feature #3991: Tool should ignore VCS artifacts when buiding new module

0.3.3

0%

0 closed (0%)   1 open (100%)

Related issues
Feature #3879: Tool's metadata should contain license info and site should display it

0.3.4

No issues for this version

0.3.5

100%

1 closed (100%)   0 open (0%)

Related issues
Feature #4847: Tool should be able to use http_proxy

0.4

25%

1 closed (25%)   3 open (75%)

Related issues
Bug #8506: PMT cannot install modules with hyphens in their name
Feature #3586: Site's watches should be implemented
Feature #3749: Site should provide feed of recent releases
Feature #3815: Site should track and display watchers for a module

0.5

0%

0 closed (0%)   3 open (100%)

Related issues
Feature #3635: Site should allow users to contact module maintainer
Feature #3696: Site should allow logged-in users to comment on a module
Feature #4126: Site should allow user to write a profile description of themselves.

really soon

85%

17 closed (85%)   3 open (15%)

Related issues
Bug #4065: Site's index pages should display the total number of associated records
Bug #4079: site incorrectly has a two character minimum project name
Bug #4083: Site should show the current release date on a module page and the associated date on a release page
Bug #4097: Site should allow underscore character in module names
Bug #4121: Site's module display page should provide alternative formatting for user-supplied headings in descriptions and release notes
Bug #4127: Site's module list should not propagate clicks on links
Bug #4380: Putting a period (".") into a tag's name should not cause the site to fail
Bug #4842: Tool errors nastily when the remote repository isn't there
Bug #4843: Tool's documentation is missing development dependencies
Bug #4844: Tool doesn't handle modules with dashes in their names
Bug #11245: Tag links on a list of modules do not behave as expected
Bug #11282: tool should create all five basic directories for a module that we teach should be present
Feature #4078: Site should provide a way to search for modules by username
Feature #4104: Site should have an "Issue tracker URL" field
Feature #4105: 2. Site's module create/edit form should recognize a github "Project homepage URL" and suggest "Issue tracker URL" for it
Feature #4292: Site should have updated puppetlabs.com menu and footer
Feature #4713: Site's navigation, menus and footers should be updated to match current puppetlabs.com site
Feature #4714: Site should have Marketo tracking code
Feature #10072: Puppet Module Tool should handle module upgrades
Feature #11979: Update existing Forge API - dependency metadata

soon

Issues that need to be resolved soon

88%

7 closed (88%)   1 open (12%)

Related issues
Bug #3588: Sign up message needs editing
Bug #3831: Site should have page titles
Bug #3905: Tool's README should be nicely formatted, even for bulletted instructions
Bug #3952: Site's module listings should display documentation using appropriately-sized fonts
Bug #3953: Site's module display should show detailed type documentation
Bug #3981: Site should have same menu contents as the main Puppet Labs site
Feature #3697: Site users should be able to subscribe to comments
Feature #3903: Site should have analytics