Sugar on a Stick/Mango Lassi: Difference between revisions

Line 116:

=== Major accomplishments this release cycle ===

* We ~~have a team!~~

* We followed the Fedora release schedule relatively well with more people understanding the process.

* We have a release schedule!

* We expanded the use of the Fedora Spins process and engineering resources, which made release engineering much smoother.

* We ~~started using~~ the Fedora Spins process and engineering resources, which made release engineering much smoother.

* Continued use of public communications channels - notably the SoaS mailing list - so things are more transparent.

* ~~We started driving~~ communications ~~to public~~ channels - notably the SoaS mailing list - so things are more transparent.

* Expanded discussion with upstream Fedora especially Fedora QA team and the new AutoQA processes. Initial integration in the Fedora Desktop QA testing process with initial guidelines and test process created. This will be expanded in Fedora 15 for the SoaS v5 release.

* ~~Multiple people have commit access to each repository that needs to be handled, so there are no single-person bottlenecks remaining~~.

* We shifted to a time-based release cycle, meaning we had a target release date set early in the process ~~rather than our prior "it seems ready~~.~~.. now-ish?" method~~.

== Press coverage ==

Feel free to add links to press coverage you find about Mango Lassi to this section.

@@ Line 116: / Line 116: @@
 === Major accomplishments this release cycle ===
-* We have a team!
+* We followed the Fedora release schedule relatively well with more people understanding the process.
-* We have a release schedule!
+* We expanded the use of the Fedora Spins process and engineering resources, which made release engineering much smoother.
-* We started using the Fedora Spins process and engineering resources, which made release engineering much smoother.
+* Continued use of public communications channels - notably the SoaS mailing list - so things are more transparent.
-* We started driving communications to public channels - notably the SoaS mailing list - so things are more transparent.
+* Expanded discussion with upstream Fedora especially Fedora QA team and the new AutoQA processes. Initial integration in the Fedora Desktop QA testing process with initial guidelines and test process created. This will be expanded in Fedora 15 for the SoaS v5 release.
-* Multiple people have commit access to each repository that needs to be handled, so there are no single-person bottlenecks remaining.
-* We shifted to a time-based release cycle, meaning we had a target release date set early in the process rather than our prior "it seems ready... now-ish?" method.
 == Press coverage ==
 Feel free to add links to press coverage you find about Mango Lassi to this section.