What naming scheme would the users like to see for releases?

[davidebeatrici]

These are the current names of the files:

softether-vpn-portable-v5.01-9667-2018.12.21-windows-x64-pdbs.zip
softether-vpn-portable-v5.01-9667-2018.12.21-windows-x64.zip
softether-vpn-src-5.01.9667.tar.gz
softether-vpn-v5.01-9667-2018.12.21-windows-x64-pdbs.zip
softether-vpn-v5.01-9667-2018.12.21-windows-x86-pdbs.zip
softether-vpnclient-v5.01-9667-2018.12.21-windows-x86_x64-intel.exe
softether-vpnserver_vpnbridge-v5.01-9667-2018.12.21-windows-x86_x64-intel.exe

We would like to adopt a clear and concise naming scheme which can be used for automated build systems.

@Andy2244 @paskal

[metalefty]

And create a directory like SoftEtherVPN-${VERSION} under the tarball. Please don't mess up current working directory.

[davidebeatrici]

I agree.

[paskal]

I like your debian packages naming and I think you can use it for all platforms.

[davidebeatrici]

softether-common_5.1.9667_amd64.deb
softether-vpnbridge_5.1.9667_amd64.deb
softether-vpnclient_5.1.9667_amd64.deb
softether-vpncmd_5.1.9667_amd64.deb
softether-vpnserver_5.1.9667_amd64.deb

You mean this one?

[metalefty]

@Andy2244 you're just repeating what i said

[Andy2244]

@Andy2244 you're just repeating what i said

Sorry just skimmed over the thread and missed your quick note about this :)

[RonNabuurs]

Like @paskal said I really like the debian package naming.
I do think you should add something like the commit hash(the short hash) for builds that do not have a tag. So when somebody builds from master you would know which version and commit they use. This would also be easier for reporting issue etc.

So something like this:
Tags:

softether-common_5.1.9667_amd64.deb
softether-vpnbridge_5.1.9667_amd64.deb
softether-vpnclient_5.1.9667_amd64.deb
softether-vpncmd_5.1.9667_amd64.deb
softether-vpnserver_5.1.9667_amd64.deb

Build from master/other branches

softether-common_5.1.9667.3b85a11_amd64.deb
softether-vpnbridge_5.1.9667.3b85a11_amd64.deb
softether-vpnclient_5.1.9667.3b85a11_amd64.deb
softether-vpncmd_5.1.9667.3b85a11_amd64.deb
softether-vpnserver_5.1.9667.3b85a11_amd64.deb

This could be achieved by using the TWEAK version option from cmake.

[Andy2244]

And create a directory like SoftEtherVPN-${VERSION} under the tarball. Please don't mess up current working directory.

The source release for 9668 is missing, softether-vpn-src-5.01.9668.tar.gz

Testing the automatic tar.gz with the new naming scheme i noticed that softether is the only package that extracts case sensitive folders, maybe this should be changed to softethervpn-${VERSION}?
I guess that's some convention of preventing case errors in scripts?

[Andy2244]

@chipitsine Quick question, i don't see the manual created source releases i use for openwrt for the last two releases 9668/9 are those just minor updates so they have none or did something change how you release versions?

[chipitsine]

@Andy2244 , they were not manual. they were supposed to be created by App Veyor, however we ran out of artifacts quota.

we are moving that to Azure Pipelines. thank for your patience

[Andy2244]

np, thanks for the info was just wondering if something broke, was changed.

[Andy2244]

@chipitsine Why does the current release still ignores what metalefty proposed?
Also 5.01.9670.tar.gz vs softether-vpn-src-5.01.9667.tar.gz ?
The archive still has no root folder like SoftEtherVPN-${VERSION} under the tarball.

[chipitsine]

@Andy2244 , sorry. lack of time

[metalefty]

This issue is still pinned. I would say this can be unpinned.