Issue tracker moved to GitHub

[magreenblatt]

The CEF and JCEF issue trackers have now moved to GitHub.

CEF: https://github.com/chromiumembedded/cef/issues
JCEF: https://github.com/chromiumembedded/java-cef/issues

[magreenblatt]

After considering available options we have decided to migrate [1] the CEF issue tracker from BitBucket to GitHub. Whether to use the existing CEF GitHub repository or to create a new issues-only repository under the chromiumembedded org is still being debated [2]. We'll notify this thread before beginning the migration, and after the migration is complete.

Migrating issues to GitHub allows access to some nice features that don't currently exist on BitBucket:

• Task lists
• Converting between issues and discussions
• Many new ways to create issues (from code lines, comments, etc)
• Finding/grouping issues by labels

[1] Migration is being accomplished using this tool (with PRs #126, #139, #140, #141, #142, #144 applied).

[2] Based on measured BitBucket/GitHub API performance we estimate that it will take approximately 5 hours to migrate all (~4000) CEF issues. There is no way to mark a public repository issue tracker as read-only -- if someone manually created an issue during the ~5 hour migration process it would mess up issue numbering (and there's no way to reset issue numbering without deleting/re-creating the repository). Making the existing public repository private while migrating would disconnect existing public forks. Using a separate issue-only repository (initially private, made public after migration) makes linking issues more complicated (need to use "org/repo#issue" syntax instead of just "#issue").

[magreenblatt]

Whether to use the existing CEF GitHub repository or to create a new issues-only repository under the chromiumembedded org is still being debated.
[...]
There is no way to mark a public repository issue tracker as read-only -- if someone manually created an issue during the ~5 hour migration process it would mess up issue numbering (and there's no way to reset issue numbering without deleting/re-creating the repository).

Looks like access to issues can be restricted using Moderation options on public repositories. We can therefore migrate issues to the existing public repository without worry of manual edits at the same time.

[magreenblatt]

Starting the import now. Github shares the same numbers for PRs and issues, so we'll lose the first 25 issues due to existing PRs on chromiumembedded/cef (not a big deal).

[magreenblatt]

Starting the import now. Github shares the same numbers for PRs and issues, so we'll lose the first 25 issues due to existing PRs on chromiumembedded/cef (not a big deal).

The import is now complete and you can see existing issues at https://github.com/chromiumembedded/cef/issues. The issue tracker will remain read-only for a bit longer, until templates have been created for new issue submission.

[magreenblatt]

Starting the import of JCEF issues now. We lose the first 10 here due to existing PRs.

[magreenblatt]

Starting the import of JCEF issues now. We lose the first 10 here due to existing PRs.

The import is now complete and you can see existing issues at https://github.com/chromiumembedded/java-cef/issues. The issue tracker will remain read-only for a bit longer, until templates have been created for new issue submission.

[magreenblatt]

CEF and JCEF issue trackers on GitHub are now enabled.