On Sat, 23 Feb 2019 at 15:48, Vladimir Sitnikov <[email protected]> wrote: > > > > 3) Tags (e.g. version tags) are located at separate branches which > > > complicates history browsing > > Can you give an example of this? I don't get what you mean. > > Please find an attached gitk view of the current Git mirror. > > In case you are not familiar with output, commits grow from the bottom > (just like regular trees do). > > It bothers me in multiple ways: > 1) V5_1_RC1, v5_1_RC2, and v5_1 tags are placed OUTSIDE of the trunk > history. In other words, if I browse "trunk" history alone, I don't > see tags at all
AFAIK, JMeter has used SVN tags in the conventional manner, i.e. they are located under tags/. I am not aware of ASF projects that do this differently. If the JMeter way of creating tags causes a problem with the history, then I suspect there is a problem with the way the JMeter Git repo was created. > 2) It is quite obscure which repository state is represented by RC. In what way? It's very clear from the SVN tags. If this is not clear from the Git version of the repo then I think something has gone awry with the conversion. > 3) V4_0 tags seem to be a complete mess (see attached > jmeter_v4_history.png). For instance, can you tell which commits are > there between V4_0_RC2 and V4_0_RC4? Can you tell why V4_0_RC5 is not > between V4_0_RC4 and V4_0_RC6? > > We don't have lots of tags, so we could even "migrate" that manually, > and it could be faster than trying to make that automatic. > What do you think? > > A bit of a side question: what is the purpose of having docs-x.y branches? It is to allow the docs for the current release to be corrected after trunk has moved on beyond the release. It is important that the online docs agree with the current release. > What is the purpose of placing generated javadocs to docs-x.y branch? Same as above; so the published Javadocs agree with the latest release. > Vladimir
