Well put, Dave!
I believe there is a majority consensus to lock down 1.0 and ship it soon.
A queue of 'required' features and fixes is starting to grow which I
suggest should go in an initial maintenance release (1.0.1? on the 1.0
branch) relatively soon after 1.0 but with a similar process so it doesn't
regress 1.0.
Glyn
David Chappell
<chappell@sonicso To: [EMAIL PROTECTED]
ftware.com> cc:
Subject: Re: What fixes are now in R
1.0?
02/10/02 20:20
Please respond to
axis-dev
All,
Given that I introduced this notion of "truckstopper" mode, I think I
should clarify what I meant by it a little better.
- Its really much more effective if its part of a larger plan that
includes things like "Feature freeze" and "code freeze". Its really
intended for a period of time ~2 weeks where no one is doing anything
but testing, getting their sanity back, and letting the release "bake"
for a while.
- Its based on a premise that *any* change, no matter how small, has the
potential to break for more than what the checkin is intended to fix.
Even a simple change like a command line parameter or a link in an html
file can lead to unexpected problems.
- It is better to ship with bugs that you know about, than to ship with
bugs that you don't know about because you were making checkins right up
to the day you ship. Is there a release note process where known bugs
can be documented with gotchas and workarounds?
- The bugs that get uncovered in the field post-FCS by the users are
usually not the ones you were so worried about at the 11th hour.
We're all experienced developers here. I'm sure I'm not saying anything
you don't already know.
Dave
Tom Jordahl wrote:
>
> Rick wrote:
> >If you want to go in "truckstopper" mode and be more selective of fixes
> >and discuss that in a conference that's fine. If you decide we are going
> >to change the way things have worked and just ignore what other people
> >request accept for the select few, shouldn't have that been voted on? :
-(
>
> Rick,
>
> Please see http://marc.theaimsgroup.com/?l=axis-dev&m=103339449319208&w=2
> and the votes that follow.
>
> I wrote:
> 3. Authorize Sam to clamp down HARD (truck stopper mode) on any source
changes - i.e.
> automatic VETO on everything unless it is a serious regression caused by
all of these
> bug fixes. Russell and myself will back him up with -1 votes on merge
requests
> (unless its one of ours of course :-).
>
> And got at 5 positive votes on that.
>
> --
> Tom Jordahl
> Macromedia Server Development
>
> -----Original Message-----
> From: Rick Rineholt [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, October 02, 2002 1:19 PM
> To: [EMAIL PROTECTED]
> Subject: Re: RE: What fixes are now in R 1.0?
>
> >Rick,
> >This was discussed in detail on the conference calls with Sam, the
release
>
> >manager, and a large number of committers. I believe you were on these
> calls.
> >The time for raising objections to the plan is not after the plan has
been
>
> >agreed upon. :-(
>
> If you want to go in "truckstopper" mode and be more selective of fixes
> and discuss that in a conference that's fine. If you decide we are going
> to change the way things have worked and just ignore what other people
> request accept for the select few, shouldn't have that been voted on? :-(
>
> >We are in closedown mode - very little to nothing goes in.
> >I think that is pretty simple. We are at T-2 days till release!
> >What fix exactly are you hot to get in? Have you convinced Sam that it
> should
> >go in? How many votes does it have? What is the risk factor?
>
> VOTE: submission to 1.0 branch: cvs commit:
> xml-axis/java/src/org/apache/axis/encoding/ser ArraySerializer.java
>
> >I will -1 any change for 1.0 that doesn't have a very low risk factor.
> >REASON: We are too close to release to make any risky changes.
>
> Rick Rineholt
> "The truth is out there... All you need is a better search engine!"
>
> [EMAIL PROTECTED]
>
> >I believe that is sufficient, don't you?
> >I also believe that others feel the same way. Others - speak up! :-)
> >--
> >Tom Jordahl
> >Macromedia Server Development
> >
> >-----Original Message-----
> >From: Rick Rineholt [mailto:[EMAIL PROTECTED]]
> >Sent: Wednesday, October 02, 2002 11:24 AM
> >To: [EMAIL PROTECTED]
> >Subject: RE: What fixes are now in R 1.0?
> >
> >No Tom, that's not what that says nor does it say that we are going to
> just
> >ignore what people have requested in.
> >What I asked has also nothing todo with the "Truckstopper" mode criteria
> >nor does that mean abandoning what we agreed on earlier namely
committers
> >requesting things put in and if someone feels no they should -1 with
> >REASON!.
> >The mode you are advocating is:
> >Sure put things on the dock, and we won't bother telling you not to,
> >because in the end we plan on loading the truck with only what we want
and
> >take just taking off. -1 to that!
> >
> >Rick Rineholt
> >"The truth is out there... All you need is a better search engine!"
> >[EMAIL PROTECTED]
> >
> >Tom Jordahl <[EMAIL PROTECTED]> on 10/02/2002 10:32:56 AM
> >Please respond to [EMAIL PROTECTED]
> >To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
> >cc:
> >Subject: RE: What fixes are now in R 1.0?
> >
> >
> >Rick,
> >See http://marc.theaimsgroup.com/?l=axis-dev&m=103339449319208&w=2
> >This plan was approved via Email and on the Conference call that
followed
> >it (which I believe you were a part of).
> >We are in truckstopper mode: Would you run after the truck taking the
CDs
> >away to fix this bug?
> >--
> >Tom Jordahl
> >Macromedia Server Development
> >
> >-----Original Message-----
> >From: Rick Rineholt [mailto:[EMAIL PROTECTED]]
> >Sent: Wednesday, October 02, 2002 10:25 AM
> >To: [EMAIL PROTECTED]
> >Subject: RE: What fixes are now in R 1.0?
> >
> >Tom,
> >I don't remember us agreeing on " automatic -1, or the overwhelming
> >agreement on inclusion". I would have -1 that plan. I think if
someone
> >has gone to the trouble of asking something to be put in and someone
> >disagrees it deserves a REAL -1 reply AND a some reason why.
> >The approach I would have liked seen is:
> >A note:
> >These fixes have been asked to be submitted to R 1.0 branch with no -1
for
> >the last two days:
> >- Fix 1
> >- Fix 2
> >etc
> >If no -1's are made by end of the day they WILL be merged in tonight.
> >If this wasn't too much of a burden.
> >
> >Rick Rineholt
> >"The truth is out there... All you need is a better search engine!"
> >[EMAIL PROTECTED]
> >
> >Tom Jordahl <[EMAIL PROTECTED]> on 10/02/2002 10:01:42 AM
> >Please respond to [EMAIL PROTECTED]
> >To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
> >cc:
> >Subject: RE: What fixes are now in R 1.0?
> >
> >
> >No fixes have been merged in to 1.0 since rc2 was built on Monday.
> >Perhaps it would help if there was a summary of fixes that are in
> >consideration?
> >My take on it is that NO src/* fixes will be approved (automatic -1 from
> >Sam) unless we have an overwhelming agreement on inclusion.
> >My take on the only two changes I wouldn't -1:
> >isConvertable() change: +1
> >- it is a regression
> >- it is low risk
> >servlet.jar change: +1
> >- 'look like dorks' bug
> >- another regression
> >- medium-low risk
> >
> >All doc/* and samples/* files should be merged from HEAD in to 1.0
before
> >the final build. It would also not be unreasonable for **/build.xml to
be
> >merged also, but this should be case by case.
> >In all cases, Sam Ruby is the final authority on what gets merged as he
is
> >the release manager.
> >--
> >Tom Jordahl
> >Macromedia Server Development
> >
> >-----Original Message-----
> >From: Rick Rineholt [mailto:[EMAIL PROTECTED]]
> >Sent: Wednesday, October 02, 2002 8:53 AM
> >To: [EMAIL PROTECTED]
> >Subject: What fixes are now in R 1.0?
> >
> >I've asked for some fixes voted into R 1.0 without any -1's and I've
seen
> >others do the same, but not sure except doing diffs and being familiar
> with
> >all the changes to determine what has been accepted in R1.0. Is there
> >another way and I just missed it? (except the diff solution :-)
> >Rick Rineholt
> >"The truth is out there... All you need is a better search engine!"
> >[EMAIL PROTECTED]
> >
> >
> >
> >
>
> Rick Rineholt
> "The truth is out there... All you need is a better search engine!"
>
> [EMAIL PROTECTED]
--
Sonic Software - Backbone of the Extended Enterprise
--
David Chappell <[EMAIL PROTECTED]> Office: (781)999-7099
Mobile: (617)510-6566
Vice President and Chief Technology Evangelist, Sonic Software
co-author,"Java Web Services", (O'Reilly 2002)
"The Java Message Service", (O'Reilly 2000)
"Professional ebXML Foundations", (Wrox 2001)
--
#### chappell.vcf has been removed from this note on October 03 2002 by
Glyn Normington
