Changes between Version 36 and Version 37 of GitMigration

Timestamp:

04/24/19 01:06:40 (6 years ago)

Author:

neteler

Comment:

+CI/CD

GitMigration

@@ -159 +159 @@
 == Future plans not being part of initial migration ==
 
+Backporting:
   * Usage of github backporting application
     * https://github.com/apps/backporting (already used by GDAL, PROJ, QGIS, ...)
+
+Zeonodo based DOIs:
   * DOI support through zenodo by connecting repos on !GitHub with Zenodo:
     * https://guides.github.com/activities/citable-code/
@@ -171 +174 @@
       * Zenodo helpdesk on DOI versioning scheme: ''Zenodo keeps the version number and date in a metadata field that you can change as you see fit even after publishing. By default Zenodo orders the releases in the order we receive them (i.e. by date). This is however only for display purposes, and it is essentially the same way !GitHub orders their releases page. In the metadata however, we do not care about ordering (because it's very hard to model the ordering correctly). We simply have a concept DOI that links to all the the specific version DOIs via !HasVersion/IsVersionOf relationship.''
       * Zenodo helpdesk on mishaps: ''...in case you make a mistake, we do have the possibility to reorder the releases manually. Naturally we would like to avoid this, however just rest assured that we can fix it if you make a mistake.''
- 
 
+CI/CD:
+  * Travis-CI: https://travis-ci.org/GRASS-GIS/grass-ci
+  * Scanning of defects, real-time: https://scan.coverity.com/projects/grass
 
+Next release:
   * Release of GRASS GIS 8.0.0 (or earlier) from !GitHub