Have An Issue To Report, But Can't Figure Out How

[Paul Nickerson]

I have an issue to report in the Puppet Community Package Repository, but I don't how to do so. The Puppet Labs issue tracker and project directory home page says "After choosing a project, use its “Issues” and “New Issue” tabs to search existing bugs and report new ones. To log new issues, you will need to register a user account and sign in." However, I have created an account and am signed in, but I see no New Issue tab.

Does anyone know how an issue should be reported?

The issue I'd like to report, BTW, is that the Puppet Windows binary package includes ruby.exe version 1.9.3.448, which according to the Common Vulnerabilities and Exposures List has vulnerability CVE-2013-4164.

[Rob Reynolds]

Paul, 

 We've patched that here https://github.com/puppetlabs/puppet-win32-ruby/pull/17 which should be included in puppet 3.4.0 forward. We are updating to the current ruby version (484). 

We are now using JIRA for reporting issues, you would do that here: https://tickets.puppetlabs.com

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/4093f7c4-2f11-4714-b191-88d0370e6cf8%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--

Rob Reynolds

Developer, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco - http://bit.ly/pupconf14
Register now and save 40%! Offer expires January 31st.

[jcbollinger]

On Monday, January 13, 2014 2:45:11 PM UTC-6, Rob Reynolds wrote:

Paul, 

 We've patched that here https://github.com/puppetlabs/puppet-win32-ruby/pull/17 which should be included in puppet 3.4.0 forward. We are updating to the current ruby version (484). 

We are now using JIRA for reporting issues, you would do that here: https://tickets.puppetlabs.com

JIRA is cool and all, but how would Joe Random visiting the PL site find it?  The "Bug Tracker" link in the top navigation bar still points to Redmine (i.e. projects.puppetlabs.com).


John

[Rob Reynolds]

Sounds like some areas haven't yet been updated. I've added https://tickets.puppetlabs.com/browse/DOCUMENT-16 (waiting to hear if this is indeed the proper location to report these outdated links) to get this updated.

 

John

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/6d4f4e92-12a9-4052-84de-b93b62bd290c%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

[Rob Reynolds]

On Mon, Jan 13, 2014 at 9:05 PM, Rob Reynolds <r...@puppetlabs.com> wrote:

On Mon, Jan 13, 2014 at 4:24 PM, jcbollinger <John.Bo...@stjude.org> wrote:

On Monday, January 13, 2014 2:45:11 PM UTC-6, Rob Reynolds wrote:

Paul, 

 We've patched that here https://github.com/puppetlabs/puppet-win32-ruby/pull/17 which should be included in puppet 3.4.0 forward. We are updating to the current ruby version (484). 

We are now using JIRA for reporting issues, you would do that here: https://tickets.puppetlabs.com

JIRA is cool and all, but how would Joe Random visiting the PL site find it?  The "Bug Tracker" link in the top navigation bar still points to Redmine (i.e. projects.puppetlabs.com).

Sounds like some areas haven't yet been updated. I've added https://tickets.puppetlabs.com/browse/DOCUMENT-16 (waiting to hear if this is indeed the proper location to report these outdated links) to get this updated.

That link looks fine to me this morning (I'm not sure if something changed or I just didn't look close enough last night). Where are you seeing Bug Tracker link point to redmine (specific urls)?

 

 

John

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/6d4f4e92-12a9-4052-84de-b93b62bd290c%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--

Rob Reynolds

Developer, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco - http://bit.ly/pupconf14
Register now and save 40%! Offer expires January 31st.

[Paul Nickerson]

Thanks for the info. Glad it's already being patched.

I got to the Redmine site through this link trail:

http://puppetlabs.com/

Open Source Projects: http://puppetlabs.com/puppet/puppet-open-source

Visit the Puppet Project homepage: http://projects.puppetlabs.com/

Click here to go to the main list of projects: http://projects.puppetlabs.com/projects

Puppet Community Package Repository: http://projects.puppetlabs.com/projects/puppet-community-pkg-repo

So currently http://puppetlabs.com/puppet/puppet-open-source has a link to Redmine.

Also, searching Google for 'puppet report bug' brings up projects.puppetlabs.com/ as the first result. You may want to put a "we're using JIRA over here now" message on that page, or do some SEO if you can.

[jcbollinger]

On Tuesday, January 14, 2014 11:00:20 AM UTC-6, Rob Reynolds wrote:

On Mon, Jan 13, 2014 at 9:05 PM, Rob Reynolds <r...@puppetlabs.com> wrote:

On Mon, Jan 13, 2014 at 4:24 PM, jcbollinger <John.Bo...@stjude.org> wrote:

On Monday, January 13, 2014 2:45:11 PM UTC-6, Rob Reynolds wrote:

Paul, 

 We've patched that here https://github.com/puppetlabs/puppet-win32-ruby/pull/17 which should be included in puppet 3.4.0 forward. We are updating to the current ruby version (484). 

We are now using JIRA for reporting issues, you would do that here: https://tickets.puppetlabs.com

JIRA is cool and all, but how would Joe Random visiting the PL site find it?  The "Bug Tracker" link in the top navigation bar still points to Redmine (i.e. projects.puppetlabs.com).

Sounds like some areas haven't yet been updated. I've added https://tickets.puppetlabs.com/browse/DOCUMENT-16 (waiting to hear if this is indeed the proper location to report these outdated links) to get this updated.

That link looks fine to me this morning (I'm not sure if something changed or I just didn't look close enough last night). Where are you seeing Bug Tracker link point to redmine (specific urls)?

 

http://docs.puppetlabs.com/
http://docs.puppetlabs.com/puppet/3/reference/
etc.

I.e. the first place I go when I want to determine whether behavior I observe or hear about is intentional or buggy.  Indeed, I rarely go anywhere else on the PL site.  As I investigate further, I see that those pages have a different header than most others at puppetlabs now do.


John

[Rob Reynolds]

The last issue was moved somewhere else, but since this falls under docs.puppetlabs.com, I believe this one may stay put this time: https://tickets.puppetlabs.com/browse/DOCUMENT-17

 

John

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/282852b9-7e67-4c99-85fa-5feb44630a34%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

[Lauren R]

Hello from your neighborhood Docs team! We've updated the headers, and the bug tracker links should point to JIRA now. Apologies for missing that in the first go-round. 

All the best, 
Lauren