[rap-dev] GitHub migration for source code and issue tracking

[Markus Knauer <mknauer@xxxxxxxxxxxxxxxxx>]

Dear Community

TL;DR
The Eclipse RAP project is now using GitHub for source code and issue tracking instead of Gerrit & Bugzilla.

The long version: Since last week we have been busy migrating the Eclipse RAP project to GitHub, rebuilding the important build jobs and hopefully updating all references in the documentation. The trigger for this was that the Eclipse Foundation will deactivate both Gerrit and Bugzilla in the (distant) future.

• Eclipse RAP now has its own "Eclipse RAP" organisation at GitHub at https://github.com/eclipse-rap/.
• The RAP Runtime Git repository can now be found at https://github.com/eclipse-rap/org.eclipse.rap - this is also the right place for new tickets. Instead of the old master branch, the current development will be found in the main branch in the future.
• The same applies to the RAP Tools Git Repository at https://github.com/eclipse-rap/org.eclipse.rap.tools.
• And of course we are happy about pull requests in the future.
  

The old Gerrit repositories will remain in read-only mode and will no longer be updated. Old bugs remain in Bugzilla, but new ones should only be created as GitHub issues for the projects.

There is currently no planning or timeline for the RAP Incubator projects. The most likely case is that we will selectively move individual projects after we have gained enough experience with the main project.

Questions, ideas and comments at any time, preferably in GitHub, but also via the usual channels like mailing list or newsgroup.

Thanks and regards

Markus