Bug migration

[Simon Stewart]

This is the vote with the options I think we should consider:

1) Migrate the existing bugs using the Google Code GH migration tool

2) Close all open Core and RC bugs, then migrate the remaining open issues.

3) As 3, but manually scan the remaining issues to identify the ones that need moving.

4) Declare bug bankruptcy.

5) Just migrate issue 141

I'll close the vote next Thursday, unless there's an overwhelming majority piling in on one option.

Simon

[Luke Inman-Semerau]

Option 4.

Google Code will still be 'open' and readable for a while... can we
just stop all new issues now on it?

> --
> You received this message because you are subscribed to the Google Groups
> "Selenium Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to selenium-develo...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/selenium-developers/CAOrAhYHS1TM0GF7sftBaA4%2B3NfEiteWQwuZn3q8vzs5bpjiLuw%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

[Jason Leyba]

Option 5.

On Thu, Mar 12, 2015 at 11:12 AM Luke Inman-Semerau <luke.s...@gmail.com> wrote:

Option 4.

Google Code will still be 'open' and readable for a while... can we
just stop all new issues now on it?

On Thu, Mar 12, 2015 at 11:04 AM, Simon Stewart
<simon.m...@gmail.com> wrote:
> This is the vote with the options I think we should consider:
>
> 1) Migrate the existing bugs using the Google Code GH migration tool
>
> 2) Close all open Core and RC bugs, then migrate the remaining open issues.
>
> 3) As 3, but manually scan the remaining issues to identify the ones that
> need moving.
>
> 4) Declare bug bankruptcy.
>
> 5) Just migrate issue 141
>
> I'll close the vote next Thursday, unless there's an overwhelming majority
> piling in on one option.
>
> Simon
>
> --
> You received this message because you are subscribed to the Google Groups
> "Selenium Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to selenium-developers+unsub...@googlegroups.com.

> To view this discussion on the web visit
> https://groups.google.com/d/msgid/selenium-developers/CAOrAhYHS1TM0GF7sftBaA4%2B3NfEiteWQwuZn3q8vzs5bpjiLuw%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Selenium Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to selenium-developers+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-developers/CAL97Zu6d119rYv2%2BCSi3ZjwwkJHfr7Eyhw%3D8q3%2B%2Bw8%3DCYFQaCQ%40mail.gmail.com.

[Alexei Barantsev]

Option 4

Regards

-- 

Alexei Barantsev

Software-Testing.Ru

Selenium2.Ru

[David Burns]

Option 4

—
Sent from Mailbox

--

You received this message because you are subscribed to the Google Groups "Selenium Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to selenium-develo...@googlegroups.com.

[Dary, Dominik]

Option4

To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-developers/1426187899683.3257781a%40Nodemailer.

[Jason Leyba]

I am horrified at the lack of support for issue 141.

All joking aside, we need to preserve this one to document that the feature is declared out of scope and won't be implemented. If we don't, it won't take long for someone to resurrect the issue.  If not recorded on the issue tracker, it should be captured in a wiki page.

To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-developers/CALcoQ9VZD_J0e-fZA45BWzKUNi7WzGHCuDrKnc%2BC5aYWYANOYA%40mail.gmail.com.

[Andreas Tolfsen]

On 12 Mar 2015, at 20:59, Jason Leyba <jml...@gmail.com> wrote:
> All joking aside, we need to preserve this one to document that the feature is declared out of scope and won't be implemented. If we don't, it won't take long for someone to resurrect the issue. If not recorded on the issue tracker, it should be captured in a wiki page.

I agree with this. We can create a simple archive, either in a wiki page or somewhere else, of all the issues. If we don't import them, we should make sure we post them somewhere for posterities sake.

[Seva Lo]

I vote 6) Find ~all issues mentioned in the code and migrate those.

And volunteer finding and migrating. I'd potentially remove from code some references to uninteresting issues and skip migrating those.

Seva

--
You received this message because you are subscribed to the Google Groups "Selenium Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-develo...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-developers/0A1E01BD-326C-414D-94BB-E9E1ACC3A987%40mozilla.com.

[Jim Evans]

I vote for option 4. As for issue 141, there are several blog posts about the issue, and anyone is welcome to use the text of mine on the subject as part of a forthcoming wiki article.

[Kristian Rosenvold]

Option 1 or 2 as long as it's not too much hassle. I find declaring bankruptcy to be a bit disrespectful of the people who have spent significant time and effort in creating good issue reports. I'd rather just kill off all issues without testcases and less than 5 stars; but that's a different strategy.

Just closing them with a standard message and a link to file a new issue (with testcase!) at google code should do the trick ?

Kristian

2015-03-13 13:39 GMT+01:00 Jim Evans <james.h....@gmail.com>:

I vote for option 4. As for issue 141, there are several blog posts about the issue, and anyone is welcome to use the text of mine on the subject as part of a forthcoming wiki article.

--
You received this message because you are subscribed to the Google Groups "Selenium Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-develo...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-developers/e70f091a-019e-4ecd-a7eb-ec87bb6e6d84%40googlegroups.com.

[Samit Badle]

Option 4.

Even if we do, it still won't take long for some one to try an resurrect the issue. We can always declare it out of scope and close it when it comes up again.

To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-developers/CAChzDzkX1dYMWCNgKUDn-9HCHxC_uJME-a-Cw%3DxpWc87JkUTSw%40mail.gmail.com.