versioning

问题 How do I actually create a release/distro of a python package that uses a git repo tag for the versioning, using setuptools and pbr ? There is plenty of information on the basic setup and configuration required: SetupTools Documentation - setup() and setup.py configuration Python Packaging User Guide - Installing Packages PBR v3.1.1 documentation StackOverflow: How to use version info generated using setuptools and pbr But where is the simple info on how to actually create the distro? i.e. I

问题 We have a library that gets released with a different version number every couple of weeks. The problem is that in order to store the version number in our jars we have a version.txt file that just contains the version number and then gets included into the build. This seems like the wrong way to do this but I can't come up with a better solution. What is a better way to store the version number in our jar's so that if a user calls me up I can easily find out the version of our product they

问题 I have written and am maintaining a number of Wix installation source files which I use to build MSI files for distribution of my application. I have not explicitly programmed for any kind of upgrading, updating, reinstallation or anything of the kind -- there is a single feature that consists of a number of components with stable GUIDs and I have observed that at least a clean installation does what I expect it to. However, I (and anyone in possession of the MSI files I distribute) may

问题 Closed . This question is opinion-based. It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing this post. Closed 3 months ago . My question is, which version-naming scheme should be used for what type of project. Very common is major.minor.fix, but even this can lead to 4 number (i.e. Firefox 2.0.0.16). Some have a model that odd numbers indicate developer-versions and even numbers stable releases.

问题 I finally decided myself to post my problem, after a couple of hours spent searching the Internet for solutions and trying some. [Problem Context] I am developing an application which will be deployed in two parts: an XML Importer tool: its role is to Load/Read an xml file in order to fill some datastructures, which are afterwards serialized into a binary file. the end user application: it will Load the binary file generated by the XML Importer and do some stuff with the recovered data

问题 Our application is quite mature, and thus we are up to version 16. However, this can give the impression that the software is old and out of touch (how many commercial applications are there with a version 20+??) Obviously, version numbers are quite arbitrary - what do other people use? I quite like the Ubuntu approach of month.date, but I'd like to see what other strategies people use. 回答1: We tend to go with something like 1.20.5, where the 20 is, in your case, the fairly high 'release'

问题 I am trying to devise a strategy for Web Services versioning and how to handle versions from a SCM point of view. We are doing bottom-up (JAX-WS) services, and therefore have less control over the schema and can't follow some schema versioning of the best practices. My current thoughts are: 1) Major changes (non-backwards compatible): Transmitted to the API client via new service URL (URL versioning). E.g.: http://com.example/v1/MyService http://com.example/v2/MyService This causes in my

问题 I'd like to be sure if vestal_versions does support versioned associations (it seems like it doesn't) before switching out to another versioning gem that can support versioned associations e.g => has_versioning. I haven't looked at the code yet but I couldn't find anything related with versioned associations from the readme file or the issue section on github. Help would be appreciated! 回答1: (At the moment of writing this) There is an associations branch in the official vestal_versions

问题 I have a C# program that uses a native C++ COM object. Visual Studio generates an interop assembly with wrappers for the types in the COM object. Each time I recompile the C# program interop assembly has version 1.0.0.0. This is bad for the installer - sometimes we extend the COM object interfaces (add new methods at the end of some interface) so the interop assembly has to be changed. when the installer tries to update an existing installation it thinks that the interop assembly hasn't

问题 I understand that interfaces are contracts and any changes (even additions) break any dependent code. However, I could have sworn I read something a while back that one of the recent .NET versions (3, 3.5??) added a new attribute that could be applied to new interface members. This attribute allowed versioning and/or making members optional. It would have been something like: interface ITest { void MethodOne(); [InterfaceVersion(2)] void MethodTwo(); } I have looked high and low for this but