tag missing problem

[CChengjie]

I'm doing a research on tags .
We found that version 3.3 was released in Maven, but there was no corresponding tag in github, Can you help me with this?
1）What is the reason for tag's absence?（Related messages and branches are found.）

• a、This version code has problems, such as the loophole, compatibility and interface issues, etc.
• b、This version has functional problems, such as unreasonable function planning, basic function cannot be used
• c、Forgot to tag
• d、Don't care or is too trouble
• e、others，_

2） To solve this problem, we propose a method that can find the true commit of version to help developers quickly locate the problem code and fix the bug. Here are the possible true commits given by our method. Can you confirm whether or not the actual commits are included, and if not, which ones?
Is v3.3 release on commit:
['8d5c1523c3d46925e9b3979a8d63c0b9d004ed1c']

♥ This question is very important to our research. Thank you for your time!

[tdunning]

1) The cause of the missing tag is unknown. As you note, there are messages which indicate that the release was created using the maven release plugin which normally creates tags. There is, however, no corresponding tag. One possibility is that there was an error in the way that the parent pom was released to the repositories. I tried to fix this related to this #175 You can see the output of this at https://search.maven.org/artifact/com.tdunning/t-digest-parent/3.3/pom The process of releasing the parent pom may have deleted the 3.3 release tag. 2) I think that the tag that you highlighted is the correct one for the core release, but redoing the release from that point would not produce a proper parent pom.

…

On Fri, Aug 26, 2022 at 12:00 AM 东吉 ***@***.***> wrote: I'm doing a research on tags . We found that version *3.3* was released in Maven, but there was no corresponding tag in github, Can you help me with this? 1）What is the reason for tag's absence?（Related messages and branches are found.） - a、This version code has problems, such as the loophole, compatibility and interface issues, etc. - b、This version has functional problems, such as unreasonable function planning, basic function cannot be used - c、Forgot to tag - d、Don't care or is too trouble - e、others，_ 2） To solve this problem, we propose a method that can find the true commit of version to help developers quickly locate the problem code and fix the bug. Here are the possible true commits given by our method. Can you confirm whether or not the actual commits are included, and if not, which ones? Is v3.3 release on commit: ['8d5c1523c3d46925e9b3979a8d63c0b9d004ed1c'] ♥ This question is very important to our research. Thank you for your time! — Reply to this email directly, view it on GitHub <#197>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAB5E6VR4YG7RJFCEQK2OUDV3BTPFANCNFSM57VTIU6Q> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[CChengjie]

thanks for your reply！❤