versioning

We are contemplating changing the version number in the next release of an iOS app from using the traditional Major.Minor.Patch version number scheme to instead use a date based scheme such as 2012.month.patch to better reflect to our users the currency of the app. Apple's only version number guidance in iTunes Connect is as follows: The version number of the app you are adding. Numbering should follow typical software versioning conventions (for example, 1.0 or 1.0.1 or 1.1). My question - do they enforce this traditional scheme? Is there any downside to using a date based scheme? Are there

Is there a nice way to version the data types and methods in WCF services? Something like this would be nice to include a method in version 1.0 to version 4.5. [ServiceContract()] interface ITradeTrackingService { [OperationContract()] [Version(1.0, 4.5)] void PublishQuote(Quote quote); } And something simular on datatypes. Then i would like to in my url do like this: server.com/ws/2.3/ And then in my Global.asax BeginRequest do something like this: protected void Application_BeginRequest(object sender, EventArgs e) { Service.Version = someParsingOfUrl(); // return 2.3; } And then the correct

I have this code - that is returning the file version (into a struct) I'm using as example the shell32.dll but there are some values that I don't understand their meanings , and would love to get an explanation. here is the code : void GetFileVersion( PCHAR pFilePath ,PVERSION pRetVersion) { DWORD dwSize = 0; BYTE *pVersionInfo = NULL; VS_FIXEDFILEINFO *pFileInfo = NULL; UINT pLenFileInfo = 0; /*getting the file version info size */ dwSize = GetFileVersionInfoSize( pFilePath, NULL ); if ( dwSize == 0 ) { printf( "Error in GetFileVersionInfoSize: %d\n", GetLastError() ); return; } pVersionInfo

Right now, on the "All releases" page of the Python Software Foundation website, the "Download latest release" links to the Python 3.6.4 version. However, you can find on the page that the release is from the 2017-12-19 and there has been two others release since, for Python 3.5.5 and Python 3.4.8 . I understand why there is two parallel version of Python with 3 and 2.7, but I do not understand why they are multiple versions of Python 3, as it should be backward compatible with Python 3 code. x.y.Z point releases are usually bug fix releases . x.Y releases are usually feature releases, but

I have two projects in solution. One is version 3.0.0.* and the other is 2.0.0.*. I build my solution on Team City using an MSBuild script. How can I inject the build number portion of the version string into the AssemblyVersion attribute leaving the major.minor.patch as defined at dev time. To put it another way I want to manually control major.minor.patch (and the majors will differ across libs in the solution) but auto increment the build number. TeamCity will automatically manage the AssemblyVersion attributes for you, but there are a few caveats: It will totally overwrite the existing

What is the best method to determine the version number I should use for a software or component? Is there a general rule to set version numbers? I'm pretty sure it is a basic question but I didn't find anything useful after searching a while. I've been doing this as an interim until I find a better solution. I don't build many large applications, mostly reports and smaller macros, but it's still important for me to keep track of changes and versions. [Current year].[Current month].[Current day] FileName 9.7.17.rpt for example. It works for me and my boss, and it gives a value which you can

So my general problem is that I want to set the version key based on the result of a task. However the version key is set before the task is run. From what I understand I can't change the value of a key once it is set so I can't change this within my task. What I want to do is run the task as a dependency to the publish task and change the value for version. I feel like there must be a way to do this, but I have no clues at the moment. Any help would be greatly appreciated. The sbt-release plugin does this by writing an sbt file in the root of the project containing the correct version. Maybe