Migration
- Are we renaming the Namespaces?
- We are removing all the current obsolete data.
- We focus on .NET Core for future proofing.
- Are we moving the repo's or just copy over the code?
- There needs to be a core team, who have access to the tools and repo's (SDL and Community)
Git repo's
- These need to be moved to the SDL git account.
- We need a core team with access to the repo's.
- We need access to setup CI.
- We need to rename them from DD4T to DXA
- One repo per module
- Split java up in pieces as we did with .NET?
Tools
- Public CI service
- Public SonarQube.
- Docker swarm? Docker Datacenter? Docker Cloud? AWS?
- CME and CD environment we can test on (All supported versions?)
- Repository which hosts Maven, NuGet, NPM and Docker Images. We deploy there and to the Central Repo's.
- Deploy Tool?
Testing
- Unit tests with code coverage (SonarQube)
- Automated tests
- Generate a Docker Container to test new features and pull requests and run the automated tests against.
Development
- Move to fork / pull requests, not everybody is in the core team, the core team can test and accept pull requests. The core team uses the same process.
- Develop is the main branch. This is where we fork from.
- Master is the release branch
- We tag releases
- We don't run code analysis on the pull requests, this because we need a version number for it and bs pull requests will interfere with the quality of the reports.