On Wed, Nov 8, 2017 at 9:57 AM, Ivan Kelly <iv...@apache.org> wrote: > > However, I do see different projects have different convention about the > rc > > tag name. some projects are using the final tag names and dropping > > the tag if a rc doesn't pass; some projects are using tag names with > > "-rc<rc_num>", and clean up the tag names after an RC is approved. > > We have been always using the final tag names for releases, but if a rc > tag > > is preferable, we can go down in that route. > As I said before, leaving the rc off the version can really screw up > people's local maven caches. Even if they don't pull from the RC repo, > doing a mvn install will create the artifacts locally, and they'll > never be updated because maven sees it as a final version. >
I am not sure why this will screw up the caches. if a RC is approved as the final, then there is no sha change and it is final. Your local installation from a RC repo should be exactly same as the one available in the central. If a RC is not approved, then it means changes will come in next RC, if you already cache the previous RC locally, when a new RC is up, the gitsha is changed, maven will update your local cache. The point is if you produce artifacts locally using a RC should be exactly same as it is final in public. Otherwise, there is no point for review. Because the process of converting a RC to final will never be reviewed. > > So my preference would be to add an rc tag. That said, we've never > done it before, so it would be a change in policy. > "an rc tag"? Do you mean a git tag name with "-rc" suffix? or do you mean the staging artifacts version with "-rc" suffix? I have seen projects using "-rc" suffix for tag name. but I don't see projects using "-rc" suffix in the artifact version. Can you point me an ASF project that is doing in this way? If it works well in other projects, we can learn from them. > http://people.apache.org/~ivank/ > > -Ivan >
