> I'm thinking of tagging 1.2.0 for when NTS is officially official. Seems like a good plan.
I'm expecting there will be a new port number assigned for the KE server. Step 1 will be to listen on both old and new port # Step 2 is to switch the client side to default to the new port #. Step 3 is to stop listening on the old port #. I'm thinking a day or two between steps. We could complicate things with some conf options. Which one do you want to call 1.2.0? Plan B is to merge them all 3 steps and tolerate the brokenness until everybody switches to the new port number. -- These are my opinions. I hate spam. _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
