{"title":"软件发布管理","authors":"A. Hoek, R. Hall, D. Heimbigner, A. Wolf","doi":"10.1145/267895.267909","DOIUrl":null,"url":null,"abstract":"Software release management begins with receipt of a release candidate comprising a software build for a particular target software release. It ends with the step of handing off that software build and associated meta-data to a manufacturing team. No changes to the software build itself are made during this process. Information about builds, targets software releases and stock keeping units (software products) are stored using a hierarchical representation. A sequence of ordered testing and approval steps is stored and may be dynamically re-configured. A release manager automatically manages the testing and approval steps according to the sequence. Web services are used to receive meta-data about the builds and release candidates.","PeriodicalId":297962,"journal":{"name":"ESEC '97/FSE-5","volume":"7 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1997-11-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"52","resultStr":"{\"title\":\"Software release management\",\"authors\":\"A. Hoek, R. Hall, D. Heimbigner, A. Wolf\",\"doi\":\"10.1145/267895.267909\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Software release management begins with receipt of a release candidate comprising a software build for a particular target software release. It ends with the step of handing off that software build and associated meta-data to a manufacturing team. No changes to the software build itself are made during this process. Information about builds, targets software releases and stock keeping units (software products) are stored using a hierarchical representation. A sequence of ordered testing and approval steps is stored and may be dynamically re-configured. A release manager automatically manages the testing and approval steps according to the sequence. Web services are used to receive meta-data about the builds and release candidates.\",\"PeriodicalId\":297962,\"journal\":{\"name\":\"ESEC '97/FSE-5\",\"volume\":\"7 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1997-11-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"52\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"ESEC '97/FSE-5\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1145/267895.267909\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"ESEC '97/FSE-5","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/267895.267909","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Software release management begins with receipt of a release candidate comprising a software build for a particular target software release. It ends with the step of handing off that software build and associated meta-data to a manufacturing team. No changes to the software build itself are made during this process. Information about builds, targets software releases and stock keeping units (software products) are stored using a hierarchical representation. A sequence of ordered testing and approval steps is stored and may be dynamically re-configured. A release manager automatically manages the testing and approval steps according to the sequence. Web services are used to receive meta-data about the builds and release candidates.