So, how is everyone feeling about this? Are we ready for the final cutover? Are there any objections to:
* final "sync" check-in (no more after this) * removing INSTALL related files as suggested by Andreas * adding README directing users to GitHub? * place everything in Read-Only status for historical record Jeff On Monday, November 23, 2015 at 8:57:41 AM UTC-5, Jeffrey Walton wrote: > > Hi Everyone, > > With the 5.6.3 release, that's pretty much the end of the line for > Crypto++ 5.6.x. New features of the library will have changes that dictate > a minor and/or major version bump. (Also see > https://cryptopp.com/wiki/Release_Versioning). > > In about 30 days, I think we should sunset Sourceforge by changing > Sourceforge's README, and directing folks to GitHub. It should let SF > visitors know the change occurred due to Crypto++ community demand, and > also thank Sourceforge for the hosting. > > I think we should keep Sourceforge for historical record, and not request > a project removal or deletion. That's because we don't have things like > Sourceforge mailing list archives and bug tracker items (as far as I know, > only the commits were migrated to GitHub). > > Any thoughts or suggestions? > > Jeff > -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com. --- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
