Hi, On the MeeGo conference we had a BoF on Release Engineering - Auke Kok and Ryan Ware was representing RE on behalf of Rolla Selbak at this session as she couldn't make it and we had a fruitful discussion.
Here's some headlines, Auke & Ryan, please fill in/correct me if I remember some things wrong or if there's some parts you feel should be mentioned: - Marko Saukko stated Changes in repository structure are usually done notified after the fact (hurts downstream, automation) Suggestion was that now we have BOSS doing all the repository generation work, that notifications on change of this source tree/configuration could be announced. - Carsten stated there is currently no documented process on how to get a build.meego.com account, such as criteria or the likes on how to get one - Currently there is a Intel/office-centric RE (practically people sitting in same location), which leads to dead silence perception of RE internals from outside. Suggestion (from Auke and Ryan) was to start having weekly RE meetings on IRC or even a weekly newsletter on RE activities. - Current maintainers view within OBS is confusing. Packages/Maintainers list exist - Carsten proposed that it would be good to have a ARM release engineer to help out with things in that area/lessen load on Intel RE, some discussion were made if he/she needs to be nominated by TSG to do s. - Sponsored uploads (helping someone upload package changes to MeeGo) was briefly discussed, as an avenue to help show worth as release engineer/packager - QA-RE interface can be improved. There's cases where QA reports show definate breakage and packages are let into Trunk anyway, leading to regression (this has gotten better, though) - David Greaves mentioned there's not much documentation/mention of how meego.com themselves uses platform tools such as BOSS and would like visibility into this to feed back into his own work. - URL links on download.meego.com/ where briefly discussed (there are repositories but they're not listed there). Google bots and other crawlers listed as issue - Anas Nashif (as Distribution Architect) is not mentioned on governance anywhere, but is a central person of responsibility/power and should be mentioned on governance pages (Note from self: Rolla should be listed as well) - David Greaves raised issue about version numbers, that it's difficult to correspond changelog entries to packages (see other thread regarding it). Difficult to tell when a security fix came in for instance - Andre Klapper raised topic on release blockers and who handles them. Change Control Board/CCB process was practically undocumented and invisible for 1.2, should definately improve for 1.3. BR Carsten Munk _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
