Optimal release time of improved versions of software packages
Information and Software Technology - Software quality assurance
Discovering models of software processes from event-based data
ACM Transactions on Software Engineering and Methodology (TOSEM)
Agile software development ecosystems
Agile software development ecosystems
Enactment Control in Interact/Intermediate
EWSPT '94 Proceedings of the Third European Workshop on Software Process Technology
Using Little-JIL to Coordinate Agents in Software Engineering
ASE '00 Proceedings of the 15th IEEE international conference on Automated software engineering
Populating a Release History Database from Version Control and Bug Tracking Systems
ICSM '03 Proceedings of the International Conference on Software Maintenance
Optimal Release Time of Computer Software
IEEE Transactions on Software Engineering
Subversion 1.5: A case study in open source release mismanagement
FLOSS '09 Proceedings of the 2009 ICSE Workshop on Emerging Trends in Free/Libre/Open Source Software Research and Development
Validity concerns in software engineering research
Proceedings of the FSE/SDP workshop on Future of software engineering research
Proceedings of the 33rd International Conference on Software Engineering
Experiences mining open source release histories
Proceedings of the 2011 International Conference on Software and Systems Process
Unifying microprocess and macroprocess research
SPW'05 Proceedings of the 2005 international conference on Unifying the Software Process Spectrum
| Hi-index | 0.00 |
The release and deployment phase of the software development process is often overlooked as part of broader software engineering research. In this paper, we discuss early results from a set of multiple semi-structured interviews with practicing release engineers. Subjects for the interviews are drawn from a number of different commercial software development organizations, and our interviews focus on why release process faults and failures occur, how organizations recover from them, and how they can be predicted, avoided or prevented in the future. Along the way, the interviews provide insight into the state of release engineering today, and interesting relationships between software architecture and release processes.