... | ... | @@ -65,7 +65,7 @@ Throughout the entirety of this timeline, the IT team will use mailng lists, [ec |
|
|
|
|
|
Notify projects that:
|
|
|
|
|
|
* ~~project websites will be moved to eclipseprojects.io, (with redirects) and once the move is complete we will begin migrating project website repos to Gitlab in Q3 ~~
|
|
|
* ~~project websites will be moved to eclipseprojects.io, (with redirects) and once the move is complete we will begin migrating project website repos to Gitlab in Q3~~
|
|
|
* If your project moves before this work is complete, you will need to create a [CI job to publish it's website content](https://wiki.eclipse.org/Jenkins#How_to_build_my_project.27s_website_with_Jenkins.3F).
|
|
|
* ~~new Gerrit repos are no longer available, only Gitlab/Github repos will be created (some exceptions for legacy projects etc)~~
|
|
|
|
... | ... | @@ -73,7 +73,7 @@ Notify projects that: |
|
|
|
|
|
Move project website repos. This will require:
|
|
|
|
|
|
* ~~Changes to the checkout script ~~
|
|
|
* ~~Changes to the checkout script~~
|
|
|
* ~~A modification to projects.eclipse.org to allow the specification of a ‘website repo’~~
|
|
|
* NOTE: Only projects that are actually using their website repositories will be moved. If a project website repo contains only the default redirection to projects.eclipse.org that repo will be replaced with a server-side redirection to projects.eclipse.org. Currently it appears that \~50% of projects use projects.eclipse.org as their default website.
|
|
|
|
... | ... | |