On 30/07/13 19:49, Claude Warren wrote:
What is the policy for updating the tag. I have a fix for JENA-488 that I
would like to apply to 2.10.1 (and get the jar redeployed) as well as the
trunk. Is there any issue with doing this?
Once binaries are released, they are frozen. Two reasons:
1/ Maven does not allow or except releases to change - SNAPSHOTs yes,
releases, no. Once downloaded there is no requirement to check again.
2/ Apache releases (which are source code) are frozen for the downstream
redistributors. This is less of an issue for Java projects because
there are project produced (avoiding the word "officially" here)
binaries but only because of (1).
The project votes to release a specific set of source bytes and if a fix
is need, the way to do it is to re-release with a new version number.
Similarly, tags for releases should be considered fixed - they are part
of the vote.
If you fix it in svn, it'll be picked up by the nightly build of
2.10.2-SNAPSHOT. Is that OK? Or do you need a release for some reason?
Andy
Claude
