It doesn’t always go smoothly, of course. This sounds good, but is this really the way it works? As with all projects and processes this is a rosy picture of the perfect release workflow, when everything goes smoothly. To ensure a continuous transfer of knowledge, and to avoid reinventing the wheel with each release, the rotation requires that one of the assignees was also assigned to the previous release, and the other assignee will be on the following release. We all do! Since our release process is not yet 100% automated, it requires a technical person to be involved, so the responsibility of pressing the buttons is rotated among the developers, with two assigned per release.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |