versioning

Must I enable versioning in my first release in order to use lightweight migration in subsequent releases?

由 自作多情 提交于 2019-12-06 09:08:26
My fear is the change of the data model in subsequent releases. I created a new xcdatamodel file in Xcode which is not versioned by default. I know you can click somewhere and make it "the first version". In the Groups and Files tree the xcdatamodel file gets a thick black arrow on the left side which you can click to see all the versions inside. My file does not have that thick arrow so is not versioned. Does this cause big problems later? Is it needed to version it right from the start to make lightweight migration work later? Once the app is shipped to users this can't be changed anymore.

What is your preferred style of product version number and why?

由 ≡放荡痞女 提交于 2019-12-06 08:16:23
Is it Major.Minor.Release - IBM style (eg. 1.2.3)? Is it the Year? (Windows '98) Something else? Reference: http://en.wikipedia.org/wiki/Versioning Presently I use major.minor.release.internal-release Example 01.12.02.19 For the next product, I was thinking of making it simpler Version-Build Example v1-b22 Before I finalize ('cause I will have to live with my decision for the rest of the product's life) I want to get as many points of views as I can. Thanks much! [major].[minor].[patch] For example: 2.0.4 Major is incremented when the product has many new, major features, minor is incremented

semantic versioning of API bundle

由 一曲冷凌霜 提交于 2019-12-06 07:44:53
When starting with a package versioned at 1.0.0 in an API bundle, what should the new version be after adding a new interface to said package? The whitepaper makes this statement regarding compatibility: It should be obvious that binary compatibility plays an important role in backward compatibility. However, backward compatibility is also very dependent on the semantics. If the responsibility of an interface changes it could still be binary compatible but no longer be backward compatible. At the same time... 3.micro — A difference in the micro part does not signal any backward compatibility

Increment the build number automatically

由 强颜欢笑 提交于 2019-12-06 07:07:00
问题 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. 回答1: TeamCity will automatically manage the

How to make version autoincrement in the latest .NET Core tooling?

由 梦想与她 提交于 2019-12-06 06:57:17
问题 I am using the latest (as of today) .NET Core tooling. There, you specify version in an <Version> MSBuild property. However, unlike [assembly:AssemblyVersion], this does not appear to support wildcards. How do I make version increment automatically in the same way? Explaining why this is a bad idea, and what should be done instead would also be a good answer. 回答1: The Version property in MSBuild does not support asterisks (wildcard) format as project.json did. However, with MSBuild you can

Why are they some new releases of Python 3 on older Python 3 versions?

由 ≯℡__Kan透↙ 提交于 2019-12-06 06:46:40
问题 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.

PaperTrail: info_for_paper_trail outside the context of a controller

由 孤者浪人 提交于 2019-12-06 06:18:29
问题 I am using the paper_trail gem for versioning my models. So far, my model depends on the info_for_paper_trail method in ApplicationController : class ApplicationController < ActionController::Base # Extra columns to store along with PaperTrail `versions` def info_for_paper_trail { revision_id: @revision.id, revision_source_id: @revision_source.id } end end This works great in context of the controller, but is there a way that I can replicate this sort of thing outside the context of the

Clearing App Data on update

由 こ雲淡風輕ζ 提交于 2019-12-06 05:45:45
问题 I need to clear(equivalent to Clear Data in App Settings ) all the old data in the app programmatically when the user updates the app from Google Play Store or any other sources. This is because I don't need any of the existing data from the old app since I have changed everything in the new app compared to the old one. I thought of implementing a version check at the app startup, but I can't find a way to get the app's previous versionCode or versionName . The only way I figured out to clear

I can't undo changes to some resources in RTC, because they're “out of sync with the file system”. Help please :(

由 大兔子大兔子 提交于 2019-12-06 05:44:22
I made changes to some files i had in a project (they were auto generated with a tool). I want to roll back those changes, but when i click "undo" an error message appears, telling me that "Problems occurred running undo local changes", reason "Resource is out of sync with the file system". Now i'd really like to undo my changes :| Anyone have any ideas? Thx VonC You should be able to: launch a refresh sandbox (that will not commit anything), as shown in your previous question " Why aren't my pending changes being shown in RTC? " then undo your local changes This thread on jazz.net has a more

How to remove local git history after a commit?

由 亡梦爱人 提交于 2019-12-06 05:20:50
问题 I would like to switch from Dropbox to the open source Sparkleshare. It uses git for the syncing and versioning. If say I had a 1GB file I deleted in my folder, it stays within the history of the local .git folder. But I would like to have this kind of heavy data on the server and not the client. How can I commit my repository and delete the local one with git? Many thanks! 回答1: Solution removing the history git fetch --depth=1 to prune the old commits. This makes the old commits and their
订阅 versioning