By convention (and also recognized by jcheck), we mark the GA of release NN with an NN-ga tag, pointing to the commit of the last build number for that release. So for example, an 11-ga tag would be created and would point to the same commit as does the 11+26 tag. Similarly, the 13-ga tag would point to the same commit as does the 13+14 tag.
Now that we have started using branches in the same repo, this will be especially helpful in identifying the GA of the feature release and distinguishing it from an update release.
We need to start doing this no later than openjfx14 GA, and should go back and do it for the older 11-dev as well.
It is not worth the effort for 13-dev unless we decide to import the jfx13 branch info the jfx repo (which is currently unplanned).
Now that we have started using branches in the same repo, this will be especially helpful in identifying the GA of the feature release and distinguishing it from an update release.
We need to start doing this no later than openjfx14 GA, and should go back and do it for the older 11-dev as well.
It is not worth the effort for 13-dev unless we decide to import the jfx13 branch info the jfx repo (which is currently unplanned).
- relates to
-
JDK-8180946 Use Mercurial tags to identify GA builds
- Closed