Create release version number problem

SteveGTR

The recent DM release seems to fix a timeout issue I was experiences when it attempts to load the web site version information. Now it comes up really quickly.

Maybe that is why the incorrect version number is being filled in for our project sometimes.

Scenario:

Database packages have version numbers formatted as 0.yyyymmdd.buildnumber

Website package version numbers drive the package version numbering and have the format n.n.n.buildnumber. The latest version number and last release are 2.3.0.178

When create a release where database version 0.20131113.6 and web site version 2.3.0.179 are available, sometimes 0.20131113.6 will be selected as the next version and sometimes 2.3.0.179 will be selected.

It was my understanding that the higher of the two version numbers would be selected, as we have designed the version numbering to be driven by the website version.

It looks like the problem results because sometimes the database versions are loaded before the website versions and sometimes the website versions are loaded prior to the database version. Whatever control is loaded last is used as the default version number for the release.

James B

Hi Steve- I've just set up a quick test with a DB and Web package, and versions as you describe.

Unfortunately, I'm seeing the same random behaviour with the versioning of the release. I'll log a bug for this and follow up with the team tomorrow on it.

SteveGTR

Thanks James. This is just problematic and can be easily overcome.

Has anyone have any ideas on the other post I made? This isn't easily overcome. Sure, I can manually finish the deployment, but...

James B

Yep, we're looking into the other post you made. It's been seen very intermittently by our internal team here but is occurring within a 3rd party component rather than our own code, making it harder to track down. One possibility is a recent windows update having an effect, although that's not proven as yet.

david.conlin

Hi Steve -

I'm very sorry about this bug, it was my fault.

I'll make sure that we ship a fix when we release next Wednesday.

david.conlin

Hi Steve -

We shipped a fix for this bug yesterday, as part of version 2.3.8. Sorry it took a bit longer than expected.

SteveGTR

Thanks David