not really actually. we really need docs for the facility BTW. like _really_ really.
BTW, here's a SO question you might want to take a look at http://stackoverflow.com/questions/3531770/including-exception-details-when-using-a-castle-wcf-facility-hosted-service W dniu 23 sierpnia 2010 10:54 użytkownik Craig Neuwirt <[email protected]> napisał: > Thanks. That's pretty much what I did. I didn't mess with TeamCity. Did > that stuff take much time? > > 2010/8/22 Krzysztof Koźmic <[email protected]> >> >> Well, ok. >> >> 1. I made sure everything compiles and all the tests run for each of 5 >> versions I released. >> 2. I went to TeamCity and set TeamCity build counter to the same >> number for each version so that they all get released with the same >> number (2.5.0.2108) (I picked date because it seemed like a better >> choice than any other arbitrary number - in the future I suggest we >> use #number of revisions since last release) >> 3. I updated changes.txt changing first line from "unreleased" to "2.5 >> (date)" >> 4. I downloaded all the files from team city and packaged them into >> .zip, adding all additional files, like license.txt, committers.txt >> (do we plan to update the file, there's a lot of people on the list I >> haven't seen around for a while), changes.txt and breakingchanges.txt. >> I also made subfolder for each of the 5 versions we ship, and I put >> all the non-mandatory binaries (facilities, for Windsor, Logging >> Components for Core) in subfolders, because I had feedback from people >> that they are confused and it's not obvious what assemblies are >> optional, which are mandatory) >> 5. I uploaded the files to SourceForge, created folders for the >> release and placed the files there >> 6. I pinned the builds in TeamCity. >> 7. I created a tag (2.5.0) for each of the releases in Git >> 8. I created a branch (2.5.x) for each of the releases in Git >> 9. I created a blogpost with announcement, as well as announced the >> release on Users and Devel group >> 10. (DIDN'T PUSH YET) I updated the mainsite news with the >> announcement, I updated the Downloads page with new links, and I >> updated the Projects page with new links dates and tentative release >> date for v3 (TBD for many people is as good as "The project is dead" >> so I'm trying to keep the impression that the project is being >> developed). >> 11. I created release notes page in the >> wiki:http://stw.castleproject.org/Windsor.Windsor_25_release_notes.ashx >> 12. I created a page in the wiki that describes sample app we have >> (just one so far) >> >> http://stw.castleproject.org/Windsor.Silvertlight_Sample_App_Customer_contact_manager.ashx >> (the page is work in progress, I didn't have time to finish it) >> 13. There's probably something I forgot about :) >> >> >> 2010/8/23 Craig Neuwirt <[email protected]>: >> > Hey Krzysztof, >> > >> > While this painful process is in your head, would you mind sharing it >> > with me since I plan to now release WCF Facility. In particular, have you >> > been maintaining any of the git commands procedures you had to do. Just >> > curious to compare against what I did and see if we can at leasts >> > commonlize >> > the steps. >> > >> > craig >> > >> > On Aug 22, 2010, at 6:26 AM, Krzysztof Koźmic wrote: >> > >> >> Hey, >> >> >> >> having gone throuh the pain of releasing Core and Windsor today I >> >> wanted to say one thing - it's extremely painful to go thought. All the >> >> (many) steps are manual and require a lot of time to complete. It took me >> >> half of the day to get it all working and out the door. That's not how it >> >> should be. I chatted with Roelof and he proposed that we should look into >> >> automating as much of the process as possible. I couldn't agree more. >> >> >> >> We should also change how we assing build numbers. Currently we use >> >> autoincremented builds count from TeamCity which has the drawback that if >> >> we >> >> release several version of the same project (for .NET 3.5, 4.0, 4.0 CP, >> >> two >> >> versions of SIlverlight, possibly Mono in the future) all of them have >> >> different numbers. For the release I manually set up the counter to be the >> >> same for all builds but we should have it done automatically. >> >> >> >> This is a major issue and to keep shipping the software on a >> >> sustainable pace we need to streamline and automate it a lot. >> >> >> >> Comments and ideas welcome. >> >> >> >> 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. >> > > -- > 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.
