Choosing the right Release management & Branching strategy
I am working on a project wherein we are to use SVN as a source repository and we need to identify a branching strategy. I am aware of branch by release & branch by feature strategies to certain extent but I am no expert and I am not sure which one or if at all either is more suitable to our requirement.
How to propagate data changes between dev, qa, and production
I have tools for propagating database definition changes, but any data changes I make I write scripts for and run them in each environment by hand.
How do you handle versioning in a multi-sided project?
I know it’s a broad question so I’ll try to be as specific as possible.
This question is more an “organisational” question than a technical one.
Include internal defects into the release notes?
When delivering a product, Release notes clearly contain known issues found by customer in the previous build.
But should we include defects that we, as a supplier, found during our testing, those unresolved and hence present in the build?
I mean, it makes sense to me but I would love to know what more experienced people think about that problem.
Include internal defects into the release notes?
When delivering a product, Release notes clearly contain known issues found by customer in the previous build.
But should we include defects that we, as a supplier, found during our testing, those unresolved and hence present in the build?
I mean, it makes sense to me but I would love to know what more experienced people think about that problem.
Dependency promotion strategies: siloed or orchestrated?
We have a lot of apps and web services (some public facing products, some internal and part of a private “backend”) that are interdependent on one another. Each one of these components has 4 environments (clusters of servers/nodes serving specific purposes):
Dependency promotion strategies: siloed or orchestrated?
We have a lot of apps and web services (some public facing products, some internal and part of a private “backend”) that are interdependent on one another. Each one of these components has 4 environments (clusters of servers/nodes serving specific purposes):
Dependency promotion strategies: siloed or orchestrated?
We have a lot of apps and web services (some public facing products, some internal and part of a private “backend”) that are interdependent on one another. Each one of these components has 4 environments (clusters of servers/nodes serving specific purposes):
Dependency promotion strategies: siloed or orchestrated?
We have a lot of apps and web services (some public facing products, some internal and part of a private “backend”) that are interdependent on one another. Each one of these components has 4 environments (clusters of servers/nodes serving specific purposes):
Software release question: do you refactor pre or post-release?
I work in finance and we have some calculators that I support. I can come up with programming solutions, but I don’t have a lot of software design or release management experience.