Re: [Puppet Users] Puppet Labs issue tracker migration 16 Dec 2013

[Josh Cooper]

On Mon, Dec 16, 2013 at 8:19 AM, Erik Dalén wrote:

> What is the desired workflow for submitting a pull request for a ticket?
>
>
Charlie wrapped up the documentation for this here:
http://docs.puppetlabs.com/community/puppet_projects_workflow.html If you
find issues or have questions, please let us know.


> The old field for branch seems gone and the issue status "In topic branch
> awaiting review" is gone as well.
>

Please add a issue link to the PR and set the status to "ready for merge".


> The workflow menu shows 25 different issue statuses and I have no clue
> which one to choose.
>

>
> On 10 December 2013 19:51, Eric Sorenson wrote:
>
>> Hi, as I mailed about a little while ago[1], we're migrating issue
>> tracking for Puppet Labs projects from Redmine to JIRA.
>>
>> After working through the tooling and integration concerns, we're going
>> to make the switch on 16th of December.
>>
>> More info on how this will work:
>>
>> * Everybody needs to create a new account on JIRA, since we can’t migrate
>> passwords from redmine to jira.
>> * If you were watching redmine bugs to track their progress, you will be
>> notified via email with the new location of the bug in JIRA. You'll need to
>> set yourself up to watch the bug in JIRA with your newly-created account.
>> * Some older issues that we think are obsolete will not be migrated, but
>> if we made a mistake and forgot to include your favorite bug, there will be
>> a link on each Redmine issue where you can migrate it with a single click.
>> * The Redmine instance will remain up and read-only, because there's a
>> ton of back history, outgoing links, google indexing, etc that is quite
>> valuable to keep.
>> * Projects that use github issues will also migrate, but pull request
>> workflow remains as-is.
>>
>> Please let me know if you have any additional questions.
>>
>> [1] https://groups.google.com/d/topic/puppet-users/4lV1cT6Li-M/discussion
>>
>> --
>> Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0
>> puppet platform // coffee // techno // bicycles
>>
>> --
>> 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+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/
>> msgid/puppet-users/52A762C7.8080709%40puppetlabs.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
>
> --
> Erik Dalén
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CAAAzDLcqJ800m%2BxvUsBnQgujVM22YU8zyiPGubadNz9FNpcs_Q%40mail.gmail.com
> .
>
> For more options, visit https://groups.google.com/groups/opt_out.
>



-- 
Josh Cooper
Developer, Puppet Labs

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CA%2Bu97umO55-ViszuEcjPfmcjdog47jw8Rymy_zBcEtgGRyFYSg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet Labs issue tracker migration 16 Dec 2013

[Charlie Sharpsteen]

On Monday, December 16, 2013 11:37:26 AM UTC-8, Jason Antman wrote:
>
> I've gone through and migrated most of the issues I was watching (and 
> still care about) that weren't already. 
>
> I ran into 4 issues that show up with a message of: 
>
> "This issue is currently not available for export. If you are 
> experiencing the issue described below, please file a new ticket in 
> JIRA. Once a new ticket has been created, please add a link to it that 
> points back to this Redmine ticket." 
>
> Should I do so, or is there a better way of handling this? 
>
> The issues in question are 4240, 13602, 17439 and 22902. 
>
> Thanks, 
> j antman 
>

Hi Jason,

Thanks for bringing these to our attention! Redmine to JIRA issue export 
has been enabled for:

  -  Puppet Community Package Repository
  -  Puppet Labs Modules

I have migrated 13602, 17439 and 22902. Ticket 4240 is in a project that 
has not seen significant activity for quite a while and so automatic issue 
migration will not be set up. For cases like this, we can discuss the 
status of the ticket on IRC in #puppet-dev.

Let us know if you have any more questions!

-- 
Charlie Sharpsteen
Open Source Support Engineer
Puppet Labs

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/59426220-8cb6-46b7-84d2-c6d2ad61f622%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet Labs issue tracker migration 16 Dec 2013

[Jason Antman]

I've gone through and migrated most of the issues I was watching (and 
still care about) that weren't already.


I ran into 4 issues that show up with a message of:

"This issue is currently not available for export. If you are 
experiencing the issue described below, please file a new ticket in 
JIRA. Once a new ticket has been created, please add a link to it that 
points back to this Redmine ticket."


Should I do so, or is there a better way of handling this?

The issues in question are 4240, 13602, 17439 and 22902.

Thanks,
j antman

On 12/10/2013 01:51 PM, Eric Sorenson wrote:
Hi, as I mailed about a little while ago[1], we're migrating issue 
tracking for Puppet Labs projects from Redmine to JIRA.


After working through the tooling and integration concerns, we're 
going to make the switch on 16th of December.


More info on how this will work:

* Everybody needs to create a new account on JIRA, since we can’t 
migrate passwords from redmine to jira.
* If you were watching redmine bugs to track their progress, you will 
be notified via email with the new location of the bug in JIRA. You'll 
need to set yourself up to watch the bug in JIRA with your 
newly-created account.
* Some older issues that we think are obsolete will not be migrated, 
but if we made a mistake and forgot to include your favorite bug, 
there will be a link on each Redmine issue where you can migrate it 
with a single click.
* The Redmine instance will remain up and read-only, because there's a 
ton of back history, outgoing links, google indexing, etc that is 
quite valuable to keep.
* Projects that use github issues will also migrate, but pull request 
workflow remains as-is.


Please let me know if you have any additional questions.

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



--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/52AF5676.7060401%40jasonantman.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet Labs issue tracker migration 16 Dec 2013

[Erik Dalén]

What is the desired workflow for submitting a pull request for a ticket?

The old field for branch seems gone and the issue status "In topic branch
awaiting review" is gone as well.
The workflow menu shows 25 different issue statuses and I have no clue
which one to choose.


On 10 December 2013 19:51, Eric Sorenson wrote:

> Hi, as I mailed about a little while ago[1], we're migrating issue
> tracking for Puppet Labs projects from Redmine to JIRA.
>
> After working through the tooling and integration concerns, we're going to
> make the switch on 16th of December.
>
> More info on how this will work:
>
> * Everybody needs to create a new account on JIRA, since we can’t migrate
> passwords from redmine to jira.
> * If you were watching redmine bugs to track their progress, you will be
> notified via email with the new location of the bug in JIRA. You'll need to
> set yourself up to watch the bug in JIRA with your newly-created account.
> * Some older issues that we think are obsolete will not be migrated, but
> if we made a mistake and forgot to include your favorite bug, there will be
> a link on each Redmine issue where you can migrate it with a single click.
> * The Redmine instance will remain up and read-only, because there's a ton
> of back history, outgoing links, google indexing, etc that is quite
> valuable to keep.
> * Projects that use github issues will also migrate, but pull request
> workflow remains as-is.
>
> Please let me know if you have any additional questions.
>
> [1] https://groups.google.com/d/topic/puppet-users/4lV1cT6Li-M/discussion
>
> --
> Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0
> puppet platform // coffee // techno // bicycles
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-users/52A762C7.8080709%40puppetlabs.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>



-- 
Erik Dalén

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAAAzDLcqJ800m%2BxvUsBnQgujVM22YU8zyiPGubadNz9FNpcs_Q%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet Labs issue tracker migration 16 Dec 2013

[Charlie Sharpsteen]

On Tuesday, December 10, 2013 2:37:14 PM UTC-8, John Warburton wrote:
>
> * Everybody needs to create a new account on JIRA, since we can’t migrate 
>> passwords from redmine to jira.
>>
>
> Is the JIRA link available? From the front page, Bug 
> Trackerpoints at RedMine . Or do I need to 
> hold my horses?
>
> Thanks
>
> John
>

Hi John,

Updated documentation will be rolled out alongside public access to JIRA on 
the 16th. Account creation will be opened on that day as well.

Let us know if you have any other questions about the migration!

--
Charlie Sharpsteen
Open Source Support Engineer
Puppet Labs

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/4fd99caa-b8ae-4fb8-9dce-9ddf5e489ecf%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet Labs issue tracker migration 16 Dec 2013

[John Warburton]

>
> * Everybody needs to create a new account on JIRA, since we can’t migrate
> passwords from redmine to jira.
>

Is the JIRA link available? From the front page, Bug
Trackerpoints at RedMine . Or do I
need to hold my horses?

Thanks

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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAAJLFxVyN4SOX%2Bi3t%3Dx_LaVX8EhuMEYYhcLJAa5_t3hoYN_M7A%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet Labs issue tracker migration 16 Dec 2013

[Eric Sorenson]

Hi, as I mailed about a little while ago[1], we're migrating issue 
tracking for Puppet Labs projects from Redmine to JIRA.


After working through the tooling and integration concerns, we're going 
to make the switch on 16th of December.


More info on how this will work:

* Everybody needs to create a new account on JIRA, since we can’t 
migrate passwords from redmine to jira.
* If you were watching redmine bugs to track their progress, you will be 
notified via email with the new location of the bug in JIRA. You'll need 
to set yourself up to watch the bug in JIRA with your newly-created 
account.
* Some older issues that we think are obsolete will not be migrated, but 
if we made a mistake and forgot to include your favorite bug, there will 
be a link on each Redmine issue where you can migrate it with a single 
click.
* The Redmine instance will remain up and read-only, because there's a 
ton of back history, outgoing links, google indexing, etc that is quite 
valuable to keep.
* Projects that use github issues will also migrate, but pull request 
workflow remains as-is.


Please let me know if you have any additional questions.

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

--
Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0
puppet platform // coffee // techno // bicycles

--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/52A762C7.8080709%40puppetlabs.com.
For more options, visit https://groups.google.com/groups/opt_out.