IAM ==== Name: Berkeley_Database_4.5.20 Submitter: karen.langford@sun.com Owner: Terrence Miller Interest: Robert.Stephens@Sun.COM Exposure: open Status: waiting need opinion 02/05/2008 Comment: buddy: Terrence Miller Comment: preinception Held 06/26/2007 SUMMARY ======= The Berkley DB project was derailed during previous commitment round. Rob Stephens is here to answer / respond to issues. ISSUES ======= Q: Why do they need to have 2 different versions? What does this imply for the library naming? A: The libraries are compatible. The libraries are versioned. The directory server to upgrade the database needs to run a script. User intervention is required to do this. There is no way to force an app to do an upgrade. This is why we need multiple versions of the library. Q: You need to keep all those libraries live and can't obsolete them until all users no longer use them. Do you understand that? A: Yes. Q: Do you want ARC to force people to upgrade? A: Yes, we are asking the ARC to help enforce this. Q: Are you deprecating the oldest version of this. A: No. Q: Is there a reason why we can't announce it as being deprecated? It just means we won't support it in the future. A: Yes, this is possible. ARC Recommendation: Make the oldest release v4.2 be deprecated. ARC Recommendation: In the future we would put a checker in place to see if database needs to be upgraded. This is not supported today. Project team asking ARC to support that a migration tool be used by users. In the opinion include, "this is what the clients need to do". Project team to send ARC a link with this documentation. VOTE ==== Approve - Lloyd Chambers, Mark Carlson, Tom Childers, John Fishcer, Terrence Miller, Jyri Vriki Deny - Abstain - Not Participating (NP) - THE NEXT STEP ============= TCR: Make the oldest release deprecated. Oldest version 4.2, New Version 4.5 Advice: Talk to Rod Evans; Look at linker standards. Opinion: Document upgrade procedures, Use standard libary versions.