How do I go from “here’s the zip” to a good release strategy?
I can write code, resolve dependencies, and get my program to run on my computer; I have no idea where to go from here though. How do I get the software ready for distribution?
Good Practices of writing release notes
At the delivery of every version of software we have to write a release note.
For example, here are some of the terms I add when I write a release note:
Releasing Mobile Application under multiple platforms, same time or?
I’ve always had this idea circling around until I am facing this issue.
Jenkins Paramerized Trigger + Copy Artifact
I’m working on setting up Jenkins to handle our release builds. A release build consists of a Windows installer that includes some binaries that must be built on Linux.
Are there any reasons not to accept a software deliverable as a virtual machine?
This is a question about logistics, not a technical question.
how to convince team and project manager that post-launch deployments are okay for new features
We have a site that launched and is “feature-complete”, we’ve done all that the client has asked for and fixed a few bugs post-launch. However, I noticed that our site’s home page is using 100 SQL queries, and there’s no caching. I took half a day to add caching and did it in a branch.
How to ascertain from the users if performance tuning has had the desired effect [closed]
It’s difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. Closed 11 years ago. So you’ve made some code changes that should […]
In which cases build artifacts will be different in different environments
We are working on automation of deployment using Jenkins. We have different environments – DEV, UAT, PROD. In SVN, we are tagging each release and placing same binaries in DEV, UAT, PROD. The artifacts already contains config files w.r.t each environment but I am not understanding why we are storing binaries in environment folder again. Are there any scenarios where deployment might be different for different environments.
Source code “prints” at release
Is there a best practice for how to document the source code you’re releasing?
Source code “prints” at release
Is there a best practice for how to document the source code you’re releasing?