Change to issue tracking for Forge & PL Module projects

[Ryan Coleman]

As Eric Sorenson noted earlier [1], issue tracking for most projects at Puppet Labs are moving to JIRA. This includes the Puppet Forge and the Puppet Labs modules on the Forge.

As of this morning, Forge issues in Redmine have been set to read-only and have been migrated into the FORGE project in tickets.puppetlabs.com. Each Redmine ticket will point you to its companion JIRA ticket. Here's an example http://projects.puppetlabs.com/issues/5033 -> https://tickets.puppetlabs.com/browse/FORGE-27

Issue tracking for Puppet Labs Forge modules are also moving. Most are moving from GitHub Issues but some were still being tracked in Redmine. This morning, we will update the 'Report Issues' link on each module page to point to JIRA. Please start filing new issues here: https://tickets.puppetlabs.com/browse/MODULES. We're still sorting out the software to migrate existing issues without losing critical information. Once that's ready, it'll work much like the Forge migration. 

I'll be spending some of my holiday curled up with hot chocolate, caring for each of the newly migrated issues. I'll update their states, ensure they're properly linked to internal work and try to give you some idea where they fit into 2014. If you have an issue you care deeply about, I suggest you follow it into JIRA and start watching it. 

I hope you find this transition fairly painless. Please let me know if you have any questions, concerns or suggestions. 

[1] https://groups.google.com/d/topic/puppet-users/4lV1cT6Li-M/discussion

--

Ryan Coleman | Modules & Forge | ryanycoleman on twitter & #puppet IRC

 

[Ryan Coleman]

On Mon, Dec 16, 2013 at 7:48 AM, Ryan Coleman <ry...@puppetlabs.com> wrote:

As Eric Sorenson noted earlier [1], issue tracking for most projects at Puppet Labs are moving to JIRA. This includes the Puppet Forge and the Puppet Labs modules on the Forge.

As of this morning, Forge issues in Redmine have been set to read-only and have been migrated into the FORGE project in tickets.puppetlabs.com. Each Redmine ticket will point you to its companion JIRA ticket. Here's an example http://projects.puppetlabs.com/issues/5033 -> https://tickets.puppetlabs.com/browse/FORGE-27

Issue tracking for Puppet Labs Forge modules are also moving. Most are moving from GitHub Issues but some were still being tracked in Redmine. This morning, we will update the 'Report Issues' link on each module page to point to JIRA. Please start filing new issues here: https://tickets.puppetlabs.com/browse/MODULES. We're still sorting out the software to migrate existing issues without losing critical information. Once that's ready, it'll work much like the Forge migration. 

I'd like to give you a brief follow-up on this part of the migration. Each Puppet Labs Forge module has its 'Report Issues' link changed to the JIRA where you'll find the Modules project. If you have an organizational bent, you can add a label for the particular module (like puppetlabs-firewall) or we'll do that for you when we triage. 

We have migrated (copied really) each GitHub issue into the modules project in JIRA. Unfortunately, we weren't able to add breadcrumbs from GitHub Issues to JIRA so you'll need to search for your issue over there. If that's a pain, feel free to ping @rcoleman on GitHub and I'll happily do that for you. JIRA search is pretty good though so a search of the issue title should take you right to it.

Sometime in January, after I've sent another note, we'll turn off GitHub issues for each module repo. Pull Requests will not be affected. That's remaining the same as always. Thanks for your patience and understanding with the change.

[Heidi Pio]

Hi Everyone,

Quick introduction:  I'm the Engineering Project Manager of the Puppet Labs Forge.

And a quick update to let you know that the Puppet Labs Forge and Module issue migrations from Redmine and GitHub are now complete.   GitHub issues for each module repo have been turned off.

Puppet Labs Forge issues can now be found here: https://tickets.puppetlabs.com/browse/FORGE 
And Puppet Labs Module issues can be found here: https://tickets.puppetlabs.com/browse/MODULES 

The pull request process will not change, however, the Puppet Forge Community Pull Request Review meeting has moved to Thursdays at 10am PST.  Ashley Penney has graciously offered to send out weekly updates for those meetings via the Puppet-Dev list. 

Please feel free to contact me if you have any questions about this migration or the pull request process. Thanks and have a great weekend!

[Dawn Foster]

On Fri, Mar 21, 2014 at 11:16 AM, Heidi Pio <heid...@puppetlabs.com> wrote:
> The pull request process will not change, however, the Puppet Forge
> Community Pull Request Review meeting has moved to Thursdays at 10am PST.
> Ashley Penney has graciously offered to send out weekly updates for those
> meetings via the Puppet-Dev list.

I suspect that this meeting is on Thursdays at 10am PDT, since PST
ended a couple of weeks ago?

Thanks,
Dawn Foster
Director of Community
http://puppetlabs.com/community

[Ryan Coleman]

On Fri, Mar 21, 2014 at 11:23 AM, Dawn Foster <da...@puppetlabs.com> wrote:

On Fri, Mar 21, 2014 at 11:16 AM, Heidi Pio <heid...@puppetlabs.com> wrote:
> The pull request process will not change, however, the Puppet Forge
> Community Pull Request Review meeting has moved to Thursdays at 10am PST.
> Ashley Penney has graciously offered to send out weekly updates for those
> meetings via the Puppet-Dev list.

I suspect that this meeting is on Thursdays at 10am PDT, since PST
ended a couple of weeks ago?

Yes. This thread has more on the triage and its date/time: https://groups.google.com/d/msg/puppet-dev/hsYf58pEG_E/KBEJ6UdQUGUJ

[Jason Antman]

Is there any update on the timeline for Module issue migration to Jira?

I opened https://github.com/puppetlabs/puppetlabs-mcollective/issues/124 at the beginning of March. This has now become more important to me, so I was going to look up my issue description and try to submit a PR (it should be a relatively trivial fix), but the link to the issue no longer exists, so I can't seem to find the details that I originally put there.

If the migration isn't imminent, does anyone know how to find the content of the issue that I opened, which seems to have now fallen off the face of the earth?

Thanks,
Jason Antman

--
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/969b4116-4558-4766-9d91-772a27d054c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.