incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From conflue...@apache.org
Subject [CONF] Apache OpenOffice Community > AOO 3.4.1 Reflection and Review
Date Mon, 17 Sep 2012 15:59:00 GMT
Space: Apache OpenOffice Community (https://cwiki.apache.org/confluence/display/OOOUSERS)
Page: AOO 3.4.1 Reflection and Review (https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4.1+Reflection+and+Review)

Change Comment:
---------------------------------------------------------------------
community testing

Edited by Andrea Pescetti:
---------------------------------------------------------------------
AOO 3.4.1 was our second release and this page is intended to reflect and review the development
and release process towards this release to identify areas where we can improve things for
future releases. We are still learning and trying to improve and to streamline our development
and release process. The goal is to get more and more routine and to reduce the overhead for
all people who are involved.

Initial brainstorming of things that were recognized by people:
* no working build bots, and not building the release branch
* too short time-frame between developer snapshots
* too less testing/review by the community on dev snapshots, start on RC only -> Solution:
organize interim QA sessions, even far from RC phase, to detect problems early.
* RC were not communicated clearly. It would be far better for testers to name them "RC1",
"RC2" and so on, on the download page at least.
* do we need a more formal written down release check list that we can easy reuse for every
release. What is important here?
* RAT scan should be run earlier, or even with all buildbot builds
* We should do complete license/notice review even in a minor release where only a small number
of items have changed.  Why?  Because we may have missed something in the
previous release's review.
* There are tradeoff's in how frequently we issue new Release Candidates.  Doing
it frequently helps get the latest code out faster for final testing.  But frequent
RC's increases workload and churn on those who are building and uploading the RC's. 
Perhaps the way to make everyone happy would be to trigger RC's from a buildbot?
* Some of the tests were not completed in time for the final RC.  We should try to
coordinate this better, so all anticipated/required testing is done before RC is voted on.

Change your notification preferences: https://cwiki.apache.org/confluence/users/viewnotifications.action
   

Mime
View raw message