The releases tab is messy

[zhangchicool]

The releases tab has several "draft" items that should be associated to 3.2.4 to 3.2.6 releases. Users might get confused when trying to download the correct version.

[nylander]

@kusalananda : I know Andreas was working on a clean-up of old files from the git history, which somehow posed problems with relating files to older releases(?). Would one step towards less confusion be to rename the "Draft" strings to each release, respectively? One still have to handle the presence of the other releases with the same numbers, however.

[zhangchicool]

I have managed to fix the releases from 3.2.4 to 3.2.7. Version 3.2.7 is marked as the latest, but it only has a windows executable and is lacking a mac version.

Also, I could not find executables for 3.2.7a, so I leave it as draft for now.

[nylander]

Feb 28 2020: The release currently labeled as "Latest release" is v3.2.7, which is incorrect. v3.2.7a is actually the latest release!

Suggestion: Create a new release (call it 3.2.8, "prerelease" or not, doesn't really matter) from currently working develop branch (via master). In this way, github will point to the correct "Latest release". After that, the v3.2.7a can be kept, or perhaps better, be deleted?

/J

[nylander]

Waiting for pull requests #145 #155 before new release

[nylander]

If one just click on the Edit button to the right of release v3.2.7a, then update the text in the comment field, and then save, I do believe this release will pop up again at the top of the list of releases. And with an appropriate green "Latest release" badge. @kusalananda ?

UPDATE: Tried this 20200525 without success.

[PhyloStar]

The manual mentions 3.2.8 version. Is the 3.2.8 version already released?

[kusalananda]

@PhyloStar says

The manual mentions 3.2.8 version. Is the 3.2.8 version already released?

You are looking at the manual on the develop branch. This is the branch that is not yet formally made into next release. The next release will (likely) be 3.2.8, but it has not happened yet. The reason this hasn't happened yet is due to other projects requiring our time, and to some degree due to that I personally had to be off work for a few months for health reasons.

Getting the next released done is our priority for MrBayes. We can not however say exactly when this will happen.

[PhyloStar]

Thank you for the clarification. Looking forward to the next version.