How to communicate within a company what is being Continually Deployed
I work for a small development company, 20 people total in the entire company, 3 in actual development, and we’ve adopted CD for our commits to trunk, and it works great, from a code management and up-time side. However – we’re getting flak from our support staff and marketing department that they don’t feel that they’re getting enough lead time on new features and notifications on bug fixes that could change behavior. Part of why we love the CD system is for us in development, it’s fast, we fix the bug, add the quick feature, close the Bugz and move on with our day to the next item.
Is it the job of a developer to suggest IT requirements?
I am the only developer working on a web application which is nearing to its end. Now we are looking into making it Live in maybe a couple of months time.
Keeping tech support on the latest software version
I’m the only software developer maintaining a subset of products at a small company. The main product I’m concerned with here is a web app which is installed on various clients’ machines, with a database and background processes.
Is it reasonable to insist on reproducing every defect before diagnosing and fixing it?
I work for a software product company. We have large enterprise customers who implement our product and we provide support to them. For example, if there is a defect, we provide patches, etc. In other words, It is a fairly typical setup.
Is it reasonable to insist on reproducing every defect before diagnosing and fixing it?
I work for a software product company. We have large enterprise customers who implement our product and we provide support to them. For example, if there is a defect, we provide patches, etc. In other words, It is a fairly typical setup.
Is it reasonable to insist on reproducing every defect before diagnosing and fixing it?
I work for a software product company. We have large enterprise customers who implement our product and we provide support to them. For example, if there is a defect, we provide patches, etc. In other words, It is a fairly typical setup.
Is it reasonable to insist on reproducing every defect before diagnosing and fixing it?
I work for a software product company. We have large enterprise customers who implement our product and we provide support to them. For example, if there is a defect, we provide patches, etc. In other words, It is a fairly typical setup.
Is it reasonable to insist on reproducing every defect before diagnosing and fixing it?
I work for a software product company. We have large enterprise customers who implement our product and we provide support to them. For example, if there is a defect, we provide patches, etc. In other words, It is a fairly typical setup.
Is it reasonable to insist on reproducing every defect before diagnosing and fixing it?
I work for a software product company. We have large enterprise customers who implement our product and we provide support to them. For example, if there is a defect, we provide patches, etc. In other words, It is a fairly typical setup.
Is it reasonable to insist on reproducing every defect before diagnosing and fixing it?
I work for a software product company. We have large enterprise customers who implement our product and we provide support to them. For example, if there is a defect, we provide patches, etc. In other words, It is a fairly typical setup.