Release engineering deals with all activities in between regular development and delivery of a software product to the end user, i.e., integration, build, test execution, packaging and delivery of software. Although research on this topic goes back for decades, the increasing heterogeneity and variability of software products along with the recent trend to reduce the release cycle to days or even hours starts to question some of the common beliefs and practices of the field.
RELENG 2013 is a full-day workshop that aims to provide a highly interactive forum for researchers and practitioners to interact and address the challenges of, find solutions for and share experiences with release engineering, and to build connections between the various communities. The workshop will consist of two keynotes, practitioner talks, paper presentations, working groups and a fishbowl panel for semi-structured group discussions. There will be two keynotes, one by John O'Duinn, director of Release Engineering at Mozilla Corporation and one by Roman Scheiter, director of Engineering Services at LinkedIn. These keynotes will set the stage for the workshop, introducing the challenges of modern companies related to release engineering.
In an effort to engage with practitioners, one of the co-organizers is a release engineer at Mozilla and one third of the PC consists of release engineers, so we guarantee that each paper or abstract submission receives at least one review from a practitioner.
Topics for papers and talks include but are not limited to:
- best practices for code movement (branching and integration)
- continuous integration and deployment
- build and configuration of software
- build system maintenance
- testing and reporting infrastructures
- continuous testing
- package management
- legal signoff and bill-of-materials
- delivery and deployment of software
- cloud provisioning and management
- software installers and update systems
- interaction with app stores
- principles and automated techniques for release planning
- management and monitoring of a software release
- release engineering for product lines
- devops and interaction with other project members
Technical Papers (4 pages) should identify challenges, discuss opposing viewpoints, outline processes, or present solutions related to various aspects of release engineering. These papers will be published in the electronic ICSE workshop proceedings.
Talk Abstracts (1 page) are only open to practitioners and should describe in 500 words or less, a talk on a key aspect of release engineering. These talks should be primarily experience based and should be used as a means of communicating challenges that are in need of research.
Both types of submissions should follow the ICSE formatting guidelines and should be submitted through easychair. Talk abstract authors can choose whether they organize the text into sections or just into one section, as long as they stay below 500 words and upload their abstract as a pdf file through the submission site (also provide a 2 or 3 sentences summary in the site's text box labeled "abstract").
Accepted papers and talks will have between 10 and 15 minutes for presentation at the workshop, followed by discussion.