release-management

问题 We had an incident recently where some code got released to live that was not scheduled to be released. It had obviously been checked into the trunk. Which is fine i guess as you want to 'check in early, check in often' . However in this instance it was not supposed to be released in the next release. What kind of checks / strategy / process can be put in place to avoid code being released to live prematurely. It seems to me even with Continuous Integration and Unit Tests this is a human

问题 I am trying to find a viable strategy to a following problem. We have several web projects which are dependent on our framework. Everything is stored in our SVN and has its own project with all the necessary directory structure (trunk, tags, branches). In an example - we have projects webprj01 and webprj02 and we have a framework frm01. All of those have usual SVN project structure - trunk, tags, branches. webprj01 and webprj01 are both dependent on frm01 and in real life frm01 is present as

问题 I'm wondering this because it's just dawned on me that I've never been involved with a company the provided release candidates before and I see the term being used more and more these days so I would like to be a little more clear on their implications. For anyone who has actually worked for a company who provides RC's before...does there happen to be any more formal specification for what a release candidate actual entails (like the difference between an RC and a Beta), or is it just a

问题 I am trying to replace an appSetting at release time using VSTS Release. All post on the web refer to the old release management tool or refer to the new one but mention the replace tokens task. This task does not exist so I presume it is built in. I have set up my web.config ( MyVar ) and set up my environment variables but nothing gets replaced. And here is my release: I apologise if I am being stupid but I just can't work this out, mostly due to out of date documentation. Update 2: Ok so

问题 My company builds a web application for Real Estate Institutions -- initially coded in classic ASP with an incremental migration to .NET. Essentially, its a website with backend DB, mixed with custom windows services/dll's. Pretty standard for .NET apps. In my past companies, we had a traditional software design life cycle. We built releases of our products, and when we released, ALL customers received the same code. Product requirements were filtered through our engineering team, sent to QA

问题 My last employer had developed an elaborate system which sat on top of SVN to deal with ongoing development: ( change management ) look at bugs/issues and associate them with commits when making the commit by tagging the bug id number and ( release management ) tag items in SVN as part of a specific release based on the bug/issue tracking system. This second part had a workflow associated with it to get sign-off from users/management. Then, when it came time to do the release (usually every

问题 We use the ExpressionEngine CMS (php) to create websites. For each site, we set up a subversion repository and commit the EE installation as well as any custom templates, images, javascript, etc. that are used. Included in the repository is the file containing all of the environment variables and the .htaccess file. We have a development server with a working copy of the repository updated via post-commit that we use to develop. When we are ready to release we create a branch in subversion,

问题 We use the ExpressionEngine CMS (php) to create websites. For each site, we set up a subversion repository and commit the EE installation as well as any custom templates, images, javascript, etc. that are used. Included in the repository is the file containing all of the environment variables and the .htaccess file. We have a development server with a working copy of the repository updated via post-commit that we use to develop. When we are ready to release we create a branch in subversion,

问题 I am caching some graphics onto CGLayers and then storing them in NSValue objects using @encode (so as to store them in an array). I just wanted to make sure that I handle the retain/release correctly... I cache the graphics and store them in the array something like this: // Create an NSMutableArray "newCache" CGLayerRef drawingLayer = CGLayerCreateWithContext(context, bounds.size, NULL); CGContextRef drawingContext = CGLayerGetContext(drawingLayer); // Do some drawing... [newCache addObject

问题 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 . In organisations where you have large numbers of applications, written in a myriad of languages running on innumerable platforms and databases how do folks manage the release of builds and patches, particularly when some of the releases are 3rd party? I know there a whole