Re: [ee4j-pmc] Github / Glassfish 5.1.0 branches

[Tom Jenkinson <tom.jenkinson@xxxxxxxxxx>]

This is just an aside, and perhaps you already know this but you can use the command line git log after:

git checkout tags/5.1.0 (assuming this is the tag - which is an outstanding question as to which one it should be)

According to https://wiki.eclipse.org/JakartaEE_New_Infra_Release_Job the tag would be 5.1.0-RELEASE but that tag doesn't have the commit you reference before and is from the end of December so probably not the one you are looking for.

On Mon, 4 Feb 2019 at 13:05, Paul Stanley <pj.stanley@xxxxxxxxxx> wrote:

Hello.

I’m looking at the Glassfish 5.1.0 release and trying to understand what changes actually made it in.  It appears that the glassfish-bot created two branches (5.1.0 and 5.1.0-RELEASE) in the main glassfish repository, but neither of these contain the source code that was actually released.  This is proven because both branches are missing PR 22715, but the change made it into the release.  As well as the branches the release-bot also tagged the source code with same names as those branches above.  However due to the way that the github.com works, it is not possible to view the tags when they have the same name as a branch.

Is it possible to delete the 5.1.0 branches from the main repository as they are misleading and will lead to future maintenance issues.

Cheers

Paul

_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc