We are developing a large applications which are related to business. You can find these applications similar to some ERP, CRM, etc.
My Problem: I have a signed assembly A.dll that it versioned as 1.0.0.0 I have another assembly (lets say B.dll) that references A.dll.
On a old web app I had a table with the following structure: tools(id, name, abbreviation, width, height, power, type)
In our Production environment we have JBoss running in a clustered mode with 4+ nodes. The base JBoss is present in subversion and then we have some local changes on each nodes.
After reading a lot of articles/QAs/FAQs/books I become to think that [MAJOR].[MINOR].[REV] is most useful versioning schema to
There are obvious pros of having revision number somewhere on the page (like on stackoverflow.com): easy for users to identify and report version, when they have issues; easyway to s开发者_如何学编程e
usually the prac开发者_运维百科tice is not to include binaries in source control repositories, i am using mercurial, and would like to know if anyone has experience with embedding version (minor + maj
How do I co开发者_开发技巧mpare version numbers? For instance: x = 1.23.56.1487.5 y = 1.24.55.487.2Can you use the Version class?
My application sto开发者_开发百科res large binary files (100Mb - 1Gb) that change over time on s3. I want to offer the ability to roll back or download previous versions of these files without having
I am building a Django powered web app that has a large database component. I am wondering, how would I go about continuing to develop the web app while users are using the live, production version? T