[Steve's responses in blue]
Let us add a bit more releases and it gets hilarious - I wont even go into language packs.
6.0.1 - 6.0.1 CF1 Mar 17, only came out as upgrade.
- True - and we have since made the decision to release full and incremental install kits. Please recognize that this is different from MU's, where we only produced incrementals unless the MU was slipped into the MR (because the MU was shipped very soon after the release of the MR).
6.0.2 - Jun 2, Japanese (what happend - is the primary language now japanese - there was never a 6.0.2 english)
- Since Tokyo is 14 hours ahead, it makes perfect sense that code might be released there first. In that 14 hour window, we found a ship-stopper bug (the @Formula stuff). When we fixed the problem, we had to call the release 6.0.2 CF1 because 6.0.2 had already been shipped in Japan and was binarily different from this new release.
6.0.1 CF2 - Jun 12.
- This is an interesting one. We didn't have a specific critical problem we HAD to address. But we knew that 6.0.2 was still too far away for some customers, so we shipped 6.0.1 CF2 to allow them to get come important 6.0.2 fixes that might help them continue with their ND6 deployments.
Was this a good idea, or did it simply muddy the waters?
6.5 Beta 2 - Jun 16, Remember that 6.5 in some areas refers to itself as 6.0.3.
6.0.2 CF1 - Jun 19
- This contains two fixes (only), which are reversions to fixes that went into 6.0.2. Of course, because 6.0.2 was released only in Japan, this is the release that introduced all 460 6.0.2 fixes to the world.
6.0.2 CF2 - Jun 29, someone manages to cut/paste problems that exists in 6.5 Beta 2 into 6.0.2 CF2.
- Not sure what this comment has to do with 6.0.2 CF2. This CF was released to resolve the outstanding @Formula behavioral differences between ND6 and R5. This CF also contains some important customer specific deployment issues with Domino Web Access.
6.0.1 CF3 - Aug 4 -
- This CF was released to resolve the outstanding @Formula behavioral differences between ND6 and R5. It is the correlary release to 6.0.2 CF2.
At the end of this year we should have both 6.0.1 CF5, 6.0.2 CF4, 6.0.3 CF2, 6.0.4, 6.5 CF1 and 6.5.1 at the same time .... which one would you recommend to your customers ???
- At the end of Sept, 6.0.3 and 6.5 will have shipped. The next MR will be 6.5.1 in January, 2005. The highest number CF on top of 6.0.1, 6.0.2, and 6.0.3 will be what customers should roll out. You should work with your customers to find out what works for them. It really depends on where customers are in their deployments. If they have already begun their deployments, it probably makes sense to allow them to continue forward in the 6.0.x plan. If they are still in evaluation or testing, then they should strongly consider 6.5.
I said I won't go into language packs - I was lying - for our customers I need a danish iNotes template and the latest language packs are 6.0.1 CF1 and 6.0.2 CF1. No template changes were made in 6.0.1 CF1. 6.0.2 CF1 shipped in all languages instead of 6.0.2. I'm not sure if the Danish 6.0.2 CF2 release has gone out yet.
Please be aware that 6.0.2 CF2 is the only CF that's needed translation. We have a strong sense to insert only fixes that don't require translation. We have been very successful in this endeavor.