Thanks for the "laundry-list"; Going to do a similar thing for our internal libraries using a private NuGet repo. I'll try to share my experiences as I go through it.
Aside from publishing to a private repo, I'll need to address building web application installers, multiple (per-client) branches, and the trickiest part to avoid forcing upgrading from .NET 2.0 (I still use my fork of ActiveRecord RC3, for example) as clients resist to move their web servers up. That is a true problem with NuGet, and specially the VS2010 package manager: it tends to force the latest and mightiest version of packages which may not support old framework versions, as required by your apps. Seb makes OpenWrap look like a more capable solution, but I didn't investigate it enough to see if I can't put it in our team workflow, so I don't think I'll try it soon, and I'll have no need to package things in that format. Also we use CruiseControl.NET, instead of Teamcity, and will migrate the build script from NAnt to MSBuild, which Castle also is trying to do. Have fun, Rafael "Monoman" Teixeira --------------------------------------- "The most exciting phrase to hear in science, the one that heralds new discoveries, is not 'Eureka!' (I found it!) but 'That's funny ...'" Isaac Asimov US science fiction novelist & scholar (1920 - 1992) 2011/4/1 Krzysztof Koźmic <[email protected]> > @Patrick > > Well we have really good build scripts (thanks to Roelof) for our CI build. > > However the release process we have is mostly manual and daunting and I > think we should be able to get to a point where we can just trigger a > release build on the teamcity and have that do all the release steps > including: > > - building the code (all supported .NET/Silverlight/Mono versions) > - running all the tests > - copying all the required files including license, release notes and > breaking changes list to the resulting package > - building and uploading package to NuPack and OpenWrap repositories > - tagging the code in Git and if it's a first release with this major/minor > number also creating release branch in Git > - updating the website / doing announcement on the list, but this is not as > important and can stay as a manual step for the time being. > > I may have missed some points, but that's basically it - we need to make it > as trivial to do as possible, and that's my call to action - raise your hand > if you'd be interested in helping or if you have some good ideas on how to > make the process simpler. > > > On 01/04/2011 11:30 PM, Patrick Steele wrote: > >> As someone who's only been a consumer of the Castle projects (Windsor, >> MonoRail and ActiveRecord), I don't know what the issues are. Could >> someone enumerate what current challenges we're faced with in >> building/signing/releasing Castle? >> >> And is this an issue with all of the Castle packages as a whole -- or >> each individual one? >> >> --- >> Patrick Steele >> http://weblogs.asp.net/psteele >> >> >> >> 2011/4/1 Krzysztof Koźmic<[email protected]>: >> >>> So we've discussed this already on several occasions. >>> >>> Is anyone interested in actually helping this happen? >>> >>> I'm asking for concrete ideas. >>> >>> Krzysztof >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Castle Project Development List" group. >>> To post to this group, send email to >>> [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]. >>> For more options, visit this group at >>> http://groups.google.com/group/castle-project-devel?hl=en. >>> >>> >>> > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Development List" group. > To post to this group, send email to [email protected] > . > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/castle-project-devel?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
