+1 to all
Minor nit-pick, what's the rationale behind master & development? Couldn't we assume the latest tag contains the release most stable API? And anything after that, regardless of which branch, is development and there's no guarantee about stability? And +1 for renaming from JDK8. development is thousand times better than JDK. Cheers Bruno ________________________________ From: Martin Desruisseaux <[email protected]> To: [email protected] Sent: Friday, 15 June 2018 12:37 AM Subject: git push --force applied, next step proposal Hello all A new "git push --force" has just been applied on https://gitbox.apache.org/repos/asf/sis.git with removal of files listed in SIS and INFRA tasks [1][2]. All removed files are still available on SVN. The large ones that were not backup files are in the data directory [3]. Starting from now, there will be hopefully no more history rewrite. For next steps, I propose to apply the following additional cleanup: * Delete the following tags: o 0.2-incubating o 0.2-incubating-rc2 o 0.2-incubating-rc3 * Rename the following tag: o 0.2-incubating-rc4 → 0.2-incubating * Delete the following branches (if we really need to start from an old release, we can start from the tag): o 0.1-incubating o 0.2-incubating o 0.3 o 0.4 o 0.5 o 0.6 o 0.7 o 0.8 * Rename the following branch: o JDK8 → development After those changes, the main branches would be: * development: were day-to-day commits are done. Depends on GeoAPI 4.0-SNAPSHOT. * master: the most stable branch. Depends on GeoAPI 3.0.1 official release. Any comment, objection, amendment? Martin [1] https://issues.apache.org/jira/browse/SIS-422 [2] https://issues.apache.org/jira/browse/INFRA-16577 [3] https://svn.apache.org/repos/asf/sis/data/unclassified/
