Hi, Am 08.06.22 um 16:41 schrieb F Campos Costero: > On Tue, Jun 7, 2022 at 5:22 PM Keith N. McKenna <[email protected]> > wrote: > >> Dennis Hamilton wrote: >>> Here's my recommendation. >>> >>> 1. Do not wait for 4.2. Use the available energy and volunteer >> power to advance the Guides for 4.1. >>> 2. Do not ever tie yourself to a speculative schedule not under your >> control. Not ever. >>> 3. When 4.2 ships or is ready for/in beta, ship a supplement. There are >> not supposed to be breaking changes. Probably will though. Just make a >> quick supplement that can be used in the interim before new 4.2 documents >> are available. The supplement will also earn feedback for things that >> people notice that are not covered or need to be covered better, and that >> will lead to supplement updates and also improved 4.2 documents. >>> Regards, >>> >>> - Dennis >>> >> Thanks for your recommendation Dennis. It was an approach I hadn't >> thought of. I am hoping that I will from the other members of the team >> as well so that we can come to consensus on the path. >> >> Regards >> Keith >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] > > I agree with Dennis that we should not wait for 4.2. I doubt that the > changes between 4.1.x and 4.2 will cause anything like the number of > revisions needed to update the existing guides Fortunately that's not fact... > to match the current release > and the schedule for 4.2 cannot even be guessed. Let's just plow ahead.
But that's true. Don't wait for 4.2.0. ;-) Regards, Matthias > Regards, > Francis >
smime.p7s
Description: S/MIME Cryptographic Signature
