I originally meant to do it during the week but couldn't make it. My new goal is to do it this saturday.
I just pushed updated release notes, and changed the build version in build-common/common.xml. That seems to be it, when it comes to repository formalia for a release right? (except for tagging) Is there anything regarding the nuget packaging of 3.3.0GA that should be committed before tagging? Can we update showbuildmenu or whatever it's based on so that "build release package" also builds the nuget package? /Oskar Den 17 april 2012 16:38 skrev Julian Maughan <[email protected]>: > Sounds good. If you want me to do the NuGet release I should be able to get > to it this weekend. I can also build and deploy the HTML documentation. > Unless you were hoping to get the release out before the end of the week? > > On 17 April 2012 15:30, Oskar Berggren <[email protected]> wrote: >> >> Hi, >> >> I have reviewed all the unresolved Jira issues marked as affecting >> 3.3.0CR1. Most of them were not new regressions (I have moved those to >> 3.2). The few that seemed to be new regressions have been fixed. >> Currently, there are no open bugs in Jira that describe 3.3.0CR1 >> regressions. >> >> The few changes that have been made after the candidate release are >> mostly in code paths that shouldn't be used except for very specific >> features/dialects. The exception is a change to the LINQ providers >> join handling to fix a regression. However, it seems limited enough >> that we don't need to delay the GA by doing another CR. (Let's do a >> minor release if really necessary instead.) >> >> I think we are ready to make the GA release. I can do it later this >> week. Should I go ahead and do it? >> >> >> /Oskar > >
