Justin Erenkrantz wrote:
> On 7/11/06, C. Michael Pilato <email@example.com> wrote:
>> that part of the release process at all. I'm talking about tracking the
>> portions of the release process that begin with, say, step 6 of
>> The stuff that's directly related to creating and publishing and testing
>> and blessing the release tarballs. The stuff that today is "tracked"
>> via intermittent emails and IRC conversations.
> Steps 6 through 12 should be done by the RM and should be done in
> short 'order' in one logical time sequence. So, I'm not sure how
> filing issues in IZ for each step is helpful.
Once again, you misunderstand. I didn't recommend using an issue for each
step. I recommended tracking the completion of each step in a *single issue
> The delay between each of those steps should be minutes not days or
> weeks. =)
Save for, as you noted, step 9.
> The most time consuming step is 9 which is testing the tarballs
> locally before posting to dev@svn. We ask the RM to do a quick sanity
> test on at least one platform combination before posting it. Then,
> steps 9 and 10 can be done by others on dev@svn - hence, that can be
> followed through the list. -- justin
(Sorry, Justin. I don't think you grokked my original suggestion at all,
and haven't the energy to cater to your seemingly unique needs here.)
C. Michael Pilato <firstname.lastname@example.org>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on Tue Jul 11 20:31:19 2006