Skip to main content
This forum is closed to new posts and responses. New discussions are now taking place in the IBM Developer Answers forum.
 
developerWorks
AIX and UNIX
Information Mgmt
Lotus
New to Lotus
Products
How to buy
Downloads
Live demos
Technical library
Training
Support
Forums & community
Events
Rational
Tivoli
WebSphere
Java™ technology
Linux
Open source
SOA and Web services
Web development
XML
My developerWorks
About dW
Submit content
Feedback



developerWorks  >  Lotus  >  Forums & community  >  Notes/Domino 6 and 7 Forum

Notes/Domino 6 and 7 Forum

developerWorks

  


Some Ideas & Current Issues
Eric Bickle 20.Aug.03 02:51 PM Lotus Notes
General All Releases All Platforms


The problem is not knowing which fixes were fixed where. A good example is the "Server Availability Index" that was flaged as marked fixed in the 6.0.1 CF3 but not 6.0.2 CF2 or 6.0.3.

The easiest fix is to make the "Release" field in your fix list database multi-value. If, for example, you fixed the Server Availability bug in 6.0.1 CF3, 6.0.2 CF2, and 6.0.3, you would select all three. And if you decided to create a 6.0.0 CF1 later, after you "fixed" that bug in the new CF for 6.0.0, you would just add it to the list of releases.

The main problem is people not knowing which fixes have been done where. This is compounded by the fact that the CF packs (seemingly) come out on different dates, what happens if you ship a CF for 6.0.2 and the next day find a servere fix for 6.0.1, then ship it a few days later. The users won't know which systems have actually been secured.

All of these fixes are creating a severe incremental upgrade nightmare as well. Have you ever tried upgrading a Domino 6.0.1 CF1 server to Domino 6.0.2? Get you're QA department to try it! If a 6.0.1 user upgrades to 6.0.1 CF3, then how are they supposed to upgrade to 6.0.2 or 6.0.3 if the 6.0.2 incremental installer doesn't support 6.0.1 CF3? Do they format their server and start from scratch?

While I understand the reasoning behind the critical fixes (administrators not wanting to go to new revisions), it doesn't work in real life. It creates hellish nightmares for things like the incremental updates. The new versions are patches as well and also include fixes, just not critical fixes. If an administrator doesn't trust upgrading to a new version number because of QA issues (needs additional testing, etc), then why do you expect critical fixes to be any different? I believe that there have been crashes and other severe issues with critical fixes in the past - why would administrators trust them any more in that case?

If I had my choice, I would drop the multiple critical fix branches and just have two code branches. One for the "latest" release (6.0.3) and one for the current releases critical fixes (6.0.2 CF2). That way you don't run into the "which bug has been fixed where" questions, and you don't have the incremental upgrade nightmares that thousands of Lotus administrators are currently having. Failing that, I would at the very least change the fix list database so that the "release" field is multivalue.

Thanks,
Eric Bickle




CF Madness !?! (Peter Haynes 19.Aug.03)
. . 6.0.2 CF2 Problems? (Eric Bickle 20.Aug.03)
. . . . RE: 6.0.2 CF2 Problems? (Peter Haynes 21.Aug.03)
. . . . client problems with 602CF1, no pro... (Gerco Wolfswink... 21.Aug.03)
. . RE: CF Madness !?! (Ashley Plant 19.Aug.03)
. . . . RE: CF Madness !?! (Alan Lepofsky 19.Aug.03)
. . . . . . RE: CF Madness !?! (Peter Haynes 19.Aug.03)
. . . . . . . . I believe my link answered both you... (Alan Lepofsky 19.Aug.03)
. . . . . . . . . . Nevertheless... (Nathan T. Freem... 19.Aug.03)
. . . . . . . . . . Only partially... (Peter Haynes 19.Aug.03)
. . . . . . . . . . . . Please read this... (Steve Mullen 19.Aug.03)
. . . . . . . . . . . . . . Thanks for the explanation eom> eom... (Peter Haynes 19.Aug.03)
. . . . . . . . . . . . . . CF - suggestion (Peter Haynes 19.Aug.03)
. . . . . . . . . . . . . . . . Futher... re: CF - suggestion (Nathan T. Freem... 19.Aug.03)
. . . . . . . . . . . . . . . . I think this might lead people to p... (Alan Lepofsky 19.Aug.03)
. . . . . . . . . . . . . . . . . . Sure... re: I think this might lead... (Nathan T. Freem... 19.Aug.03)
. . . . . . . . . . . . . . . . . . . . RE: Sure... re: I think this might ... (Steve Mullen 19.Aug.03)
. . . . . . . . . . . . . . . . . . . . . . RE: Sure... re: I think this might ... (Peter Haynes 20.Aug.03)
. . . . . . . . . . . . . . . . . . . . . . RE: Sure... re: I think this might ... (Nathan T. Freem... 20.Aug.03)
. . . . . . . . . . . . . . . . . . . . . . . . I think it boils down to.. (Gerco Wolfswink... 21.Aug.03)
. . . . . . . . . . . . . . . . . . . . . . . . . . *Good point. It is hard to communic... (Ben Langhinrich... 21.Aug.03)
. . . . . . . . . . . . . . . . . . . . . . . . . . * A good diagram is worth a thousan... (Andrew Price 21.Aug.03)
. . . . . . . . . . . . . . . . . . . . . . . . . . I fully agree to that. eom> eom> (Harkpabst Melia... 21.Aug.03)
. . . . . . . . . . . . . . RE: Please read this... (Bob Brodsky 19.Aug.03)
. . . . . . . . . . . . . . Hi Steve... re: Please read this...... (Nathan T. Freem... 19.Aug.03)
. . . . . . . . . . . . . . . . I understand. Any constructive sugg... (Steve Mullen 19.Aug.03)
. . . . . . . . . . . . . . . . . . Some Ideas & Current Issues (Eric Bickle 20.Aug.03)
. . . . . . . . . . . . . . . . . . Better Organized download page (Erick Grindling... 3.Nov.03)
. . . . . . . . . . . . . . I LIKE IT! (Christopher J W... 20.Aug.03)
. . . . . . . . . . . . . . . . Multiple branches of code is good, ... (Gerco Wolfswink... 21.Aug.03)
. . . . . . . . . . . . . . . . . . thanks... (Alan Lepofsky 21.Aug.03)
. . . . . . . . . . . . . . . . . . RE: Multiple branches of code is go... (Nathan T. Freem... 22.Aug.03)
. . . . . . . . . . . . . . . . . . . . Yup :-) (Gerco Wolfswink... 23.Aug.03)
. . . . . . . . . . . . . . Steve Mullen please respond (Carsten L Peder... 19.Aug.03)
. . . . . . . . . . . . . . RE: Please read this... (Wolfgang Haderl... 19.Aug.03)
. . . . . . . . . . . . . . . . Agree about the Fix List - nice sug... (Steve Mullen 19.Aug.03)
. . . . . . . . . . . . . . RE: Please read this... (Harkpabst Melia... 20.Aug.03)
. . . . . . . . . . . . . . . . RE: Please read this... (Harkpabst Melia... 20.Aug.03)
. . . . . . . . . . . . . . . . . . *How about you replicate the forum ... (Ben Langhinrich... 20.Aug.03)
. . . . . . . . . . . . . . . . . . . . Thank you, not interested. (Harkpabst Melia... 21.Aug.03)
. . . . . . . . . . . . . . . . . . . . . . They have (Ben Langhinrich... 21.Aug.03)
. . . . . . . . . . . . . . . . . . . . . . . . RE: They have (Harkpabst Melia... 21.Aug.03)
. . . . . . . . . . . . . . . . . . . . . . . . . . You have a point (Ben Langhinrich... 21.Aug.03)
. . . . . . . . . . . . . . Ta for entering the foray... Steve,... (Bill Buchan 21.Aug.03)
. . . . . . . . . . . . . . . . * Very good ideas, and well deserve... (Andrew Price 21.Aug.03)
. . . . . . . . . . . . . . RE: Please read this... (Raymond Neeves 22.Aug.03)
. . . . . . . . . . . . . . . . Tell that to pointy haired manageme... (Gerco Wolfswink... 23.Aug.03)
. . . . . . RE: CF Madness !?! (Ashley Plant 20.Aug.03)
. . . . It gets much worse - look here (Carsten L Peder... 19.Aug.03)
. . . . . . It is not that bad... (Alan Lepofsky 19.Aug.03)
. . . . . . RE: It gets much worse - look here (Steve Mullen 19.Aug.03)
. . . . . . . . RE: It gets much worse - look here (Carsten L Peder... 20.Aug.03)
. . . . CF Madness !?! LOL (Harkpabst Melia... 19.Aug.03)
. . . . . . Stop it!!! ROFL (NextHop XL 19.Aug.03)
. . . . . . RE: CF Madness !?! LOL (Sergey K Levine... 20.Aug.03)
. . . . . . . . while you're welcome to express you... (NextHop XL 20.Aug.03)
. . . . . . . . * Ignore Sergey, he is a fool. eom>... (Andrew Price 20.Aug.03)
. . . . . . . . Maybe it's time *you*... (Gerco Wolfswink... 20.Aug.03)
. . . . . . . . . . Sergey's a real "people person", no... (benpoole 20.Aug.03)
. . . . . . . . Urrgghhh! (Keil Wilson 26.Feb.04)


Document Options






  Document options
Print this pagePrint this page

Search this forum

Forum views and search


  Forum views and search
Date (threaded)
Date (flat)
With excerpt
Author
Category
Platform
Release
Advanced search

Member Tools


RSS Feeds

 RSS feedsRSS
All forum posts RSS
All main topics RSS
More Lotus RSS feeds

Resources

 Resources
Forum use and etiquette
Native Notes Access
Web site Feedback

Lotus Support

 Lotus Support
IBM Support Portal - Lotus software
Lotus Support documents
Lotus support by product
Lotus support downloads
Lotus support RSS feeds

Wikis

 Wikis
IBM Composite Applications
IBM Mashup Center
IBM Connections
IBM Connections Cloud Developers
IBM Docs
IBM Forms
IBM Mobile Connect
IBM Sametime
IBM SmartCloud for Social Business
IBM Web Experience Factory
Lotus Domino
Lotus Domino Designer
Lotus Expeditor
Lotus Foundations
Lotus iNotes
Lotus Instructor Community Courseware
Lotus Notes
Lotus Notes & Domino Application Development
Lotus Notes Traveler
Lotus Protector
Lotus Quickr
Lotus Symphony
IBM Web Content Manager
WebSphere Portal

Lotus Forums


 Lotus Forums
Notes/Domino 9.0
Notes/Domino 8.5 + Traveler
Notes/Domino XPages development forum
Notes/Domino 8
Notes/Domino 6 and 7
IBM Connections
IBM Mobile Connect
IBM Sametime
IBM SmartCloud Notes
Lotus Enterprise Integration
Lotus Protector
Lotus Quickr
Lotus SmartSuite