Team, What is our plan of release strategy for the DotNet CAS Client? I am looking at our commit log and see a number of changes have gone in since the v1 days and I would like to have the final artifact somehow show up on NuGet. We have so far been downloading the source and compiling it locally, which is less than ideal.
I found some instructions here on how to do the release: http://docs.nuget.org/docs/creating-packages/creating-and-publishing-a-pac kage Any volunteers to cut the 1.0.2 release? Any issues with cutting the release? Misagh -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
