Hi,
I would love to do it again. The first time was good, but the second
time will be even better. I'd like to have a Toronto person
(Torontian? Torontonian? Torontoite?) to work with me so that we'd
have both coasts covered.
As I said, it went pretty smoothly last time. I wouldn't want to
change much, except that I'm going to be pestering folks to check
build dependencies *way before* release day. That was the thing that
killed us last time.
Anyone want to pile on?
- Eli
On Mar 9, 2009, at 4:19 PM, Colin Clark wrote:
Hi all,
We've been refining our release process over the past few versions
of Infusion. As part of this, we've tried to pass the release
manager baton around the community, giving everyone an opportunity
to help drive our process. This time, we're looking for someone to
take on the role of release manager for Infusion 1.0.
The job of the Release Manager is to help guide and coordinate the
community through the life cycle of a release. This includes things
like:
* keeping everyone in the loop on the status of the release
* helping to organize the release tasks in the wiki, on list, and in
JIRA
* working with Justin and others to coordinate bug parade and code
freeze
* cutting the release tag, packaging up the release, and announcing
it to the community
A comprehensive list of our release process is available in the wiki:
http://wiki.fluidproject.org/display/fluid/Release+Process
Anyone can be the release manager. It does involve familiarity with
JIRA, but we can pair you up with a past release manager to help
with the work. For 0.8, we had a particularly successful tag-team
effort from Anastasia and Eli.
Let us know if you're interested in lending a hand,
Colin
---
Colin Clark
Technical Lead, Fluid Project
Adaptive Technology Resource Centre, University of Toronto
http://fluidproject.org
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
. . . . . . . . . . . . . . . . . .
.
Eli Cochran
user interaction developer
ETS, UC Berkeley
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
