versioning

问题 Problem description: In our project we have one "production database" and many "devs". We want to know how we can manage and install the changes. We already have some procedures but it takes a lot of time and sometimes causes errors. We can't lose data - so we can't use "drop table". We can only use "alter table". Our actual "db versioning procedure" is like this: We have a table named [actual_version] that contains the actual version of the installed db schema We have a file named "changes

问题 Let's say we use gRCP/Protobuf to connect many application. Those application are developped and released at their own team, with their own speed. Over time there will be different version of the the same app (e.g. desktop apps install on user PCs) that use different version on defined interface. While Protobuf is meant to allow backward compatibility, is there a way to know what version of interface is running at different points? The simplest implementation is to have interface version

问题 I understand that Microsoft uses this template when versioning their products: Major.Minor.Build.Revision. Major is changed when the "developers" want to show that there is a big change in the software and backward compatibility cannot be assumed. Maybe a major rewrite of the code is done. Minor number represents a significant enhancement with the intention of backward compatibility. Build number is a small change, for example a recompilation of the same source. Revision is used to fix a

问题 I'm new to ASP.NET but I'm looking to implement some versioning for a new API I'm about to start. I'm not even sure if what I'm looking for is possible but I'm after a very clean version method using a header variable. Ideally I want to be able to have a versions folder within the code structure and different folders containing the different API versions within that. Each version folder would contain a full copy of the core API code so I'd know there would never be any conflicts etc. I know

问题 I'm using a versioning system that is represented by a.b.build where a is the overall version (will be 0 for prototype, alpha and beta versions, 1 for major release), b is the milestone version (along the lines of representing the proto, alpha, beta stages) and build represents literally the amount of times the project has been compiled. At the moment, I have the app read from a text file, increment the number, and save to a text file when the app is run with a debug flag set. I'm looking for

问题 Would the following be a viable strategy for implementing versioning(using "example" as a sample document type): Have one original document where the type field is named example_original. Subsequent changes to the document all have type example_change and the id of example_original document as a key. The change would also carry a timestamp. Keep one doc with type example_current that is the result of example_original with all example_change "applied". A new example_change document would

问题 I am using the XMLSerializer to save this class to a file. The class has a string and an enum as shown below: public class IOPoint { string Name {get; set;} TypeEnum {get; set;} } public enum TypeEnum { Temperature, Pressure, Humidity, } When serialized it looks like this. <IOPoint> <Name>Relative Humidity</Name> <TypeEnum>Humidity</TypeEnum> </IOPoint> I've been serializing and deserializing this object with no problems for several versions. I no longer want to support Humidity, so I removed

问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 5 years ago . I previously asked about Version Cue 3 vs Subversion. I think this is a better question and someone suggested http://www.gridironsoftware.com/Flow/ I hope this question will allow others to join in and suggest other tools or give specific recommendation to using Version Que versus other tools. 回答1: Take a look

问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 5 years ago . I previously asked about Version Cue 3 vs Subversion. I think this is a better question and someone suggested http://www.gridironsoftware.com/Flow/ I hope this question will allow others to join in and suggest other tools or give specific recommendation to using Version Que versus other tools. 回答1: Take a look

问题 What are current best-practices for systematic build numbering and version number management in Java projects? Specifically: How to manage build numbers systematically in a distributed development environment How to maintain version numbers in source / available to the runtime application How to properly integrate with source repository How to more automatically manage version numbers vs. repository tags How to integrate with continuous build infrastructure There are quite a number of tools