Oops, we should fix that. I'm away from home so I won't be able to upload another package, sorry guys.
Cheers John On 17/01/2010, at 10:10, Krzysztof Koźmic <[email protected]> wrote: changes.txt in ReleaseNotes in the package says "unreleased" while it should be "2.0.0" when outlining new changes. Ken, how is it going with the "MR2 highlights" ? Krzysztof On 2010-01-16 22:58, John Simons wrote: I've uploaded it: https://sourceforge.net/projects/castleproject/files/MonoRail/2.0/Castle.MonoRail-2.0.0.zip/download On Jan 16, 10:56 pm, Ken Egozi<[email protected]> wrote: guys, I'm terribly sorry. My internet connection keeps failing, and since it's weekend I can't get tech support to look up the Cables hub. anyway, I've updated all project's version numbers to 2.0.0, and finally succeded with commit (it kept failing as the line dropped in the middle). Now I'm waiting for TeamCity to complete run. now if someone with SF access can grab the release artifacts once it's done and update SF it would be superb. after it's there I'll update the site. On Sat, Jan 16, 2010 at 11:28 AM, John Simons<[email protected]>wrote: Inline On Jan 16, 8:18 pm, Ken Egozi<[email protected]> wrote: I'm in the middle of a little enhancement to AspView, and started on writing a "MR2 highlights" text. the latter can wait. I've also started collecting latest dlls. I've already updated all dlls, did I miss any? I will *love* any help with the release. What in particular? A question comes out though. what version will the projects that are part of Monorail but MR does not depend on - Extensions (Windsor/ARSupport/TransformFilters) and the view-engines (at least Brail and AspView)? 2.0.0 I think that, going forward, since MR Core has been very stable during the last months, and most changes/requests went to the view-engines, it might be wise to allow releasing of the view engines (and maybe ARSupport also) more often than a whole MR release update. Yes agree, the more separation the better my suggestion - we *do* set them all to 2.0, and they *will* follow future MR version numbers *when* MR gets released, but we will also allow releasing the small projects separately. 2.0.0 for everything that is compiled by the Monorail project make any sense? Yes On Sat, Jan 16, 2010 at 4:16 AM, John Simons<[email protected] wrote: Monorail is now ready to be released. Ken, are you going to do it? or do you want me to do it? Cheers John On Jan 15, 8:14 pm, Krzysztof Koźmic (2)<[email protected]> wrote: Which only reminds me of one thing - we should provide a roadmap for our projects, even a rough, sketchy one, but that's sending a clear signal to everyone interested that Castle is being actively developed. On 15 Sty, 10:11, John Simons<[email protected]> wrote: Cool :) On Jan 15, 7:48 pm, Markus Zywitza<[email protected]> wrote: What's the problem? AR 2.1.1 will be released tonight and available for MR bundle. I planned to release 2.2 Alpha 1 in about 2 weeks when I have an example application for the new IConversation feature I just finished. -Markus 2010/1/15 Krzysztof Koźmic (2)<[email protected]>: That's a bummer. We should have released Validator before AR :/ Not to make two basically identical releases on the span of two days. Krzysztof On 15 Sty, 08:53, John Simons<[email protected]> wrote: That wasn't the problem. The problem is that ActiveRecord is dependant on Validator and Validator was released yesterday. On Jan 15, 5:46 pm, Krzysztof Koźmic< [email protected]> wrote: John, we have an ActiveRecord compiled against new Core released Markus released it two days ago. Krzysztof On 2010-01-15 03:02, John Simons wrote: Updated Monorail dependencies (including Boo), but it wasn't easy! Had to recompile TemplateEngine and ActiveRecord against latest Core + Validator So this means that we have 2 more releases to go before Monorail release: - ActiveRecord - TemplateEngine (I'll do this one) Also changed IEmailSender to use the one in the Core So, I think once the releases above are done, we should be good to release Monorail. Ken, what's the plan to tackle the lack of documentation, new features, breaking changes and bug fixes since the last ‘release’? Cheers John ------------------------------------------------------------------------ *From:* Krzysztof Koźmic<[email protected]> *To:* [email protected] *Sent:* Fri, 15 January, 2010 7:35:06 AM *Subject:* Re: Releasing Monorail tomorrow Ken, no problem, I don't think anyone will need it desperately over the weekend :) And if you need a hand with the release, let me know. back to Boo/Brail - do we upgrade to v0.9.3? Krzysztof On 2010-01-14 21:24, Ken Egozi wrote: @john: thx for taking care of that @Michael: as John put it, nag away :) @Krzysztof: yeah about that "tomorrow" bit. I never have set that date. I would never have as tomorrow is my deadline for doing my taxes, and I *really* do not believe that I'll be able to run the release process in a couple of hours afterwards. I did say that I will dedicate this Saturday to complete as much as I can, and hopefully do the release then. On Thu, Jan 14, 2010 at 10:22 PM, John Simons <[email protected]<mailto: [email protected]>> wrote: Applied, thanks Michael. And yes please do nag us about it, 2 years to get a patch applied is a bit too much to wait, you have all the right to nag. Cheers John ------------------------------------------------------------------------ *From:* Krzysztof Koźmic<[email protected] <mailto:[email protected]>> *To:* [email protected] <mailto:[email protected]> *Sent:* Fri, 15 January, 2010 4:09:12 AM *Subject:* Re: Releasing Monorail tomorrow Michael, You have every right to be nagging! - this patch was submitted 2 years ago. There's just one unit test exposing this issue, but since all other tests are passing I would assume it's quite safe to apply (especially that as you say - you've been field testing it for some time). Ken? John? - any reason for this to not get applied for v2.0? cheers, Krzysztof On 2010-01-14 18:02, Michael Davis wrote: Does this mean that there are no plans to address any of the remaining open issues in Donjon prior to the Monorail release? If so, are there any plans as to when these issues might be addressed? In particular, I'd like to see someone take a look at the patch I submitted for MR-ISSUE-494, since I have an application in production that relies on a fix for that problem, but it'd be nice to know what the plans are for looking at the other issues as well. The patch I made fixes the problem for my application, at least, but I'd still like someone who is more familiar with the code to look at it in case there is a better way to do things. I hate to sound like I'm nagging, and I really appreciate all the work everyone has done to get this far. I'd just like to see some indication that someone has at least looked at the remaining issues before pushing a release out the door. I can always keep making my own builds of Monorail for my application, if necessary. Thanks, Michael Davis 2010/1/14 Krzysztof Koźmic (2)<[email protected] <mailto:[email protected]>> Are we good to go tomorrow? Ken? Richard is releasing his components today, and IIRC these are the only things stopping MR from getting released? -- 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 ... read more » -- 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. __________________________________________________________________________________ See what's on at the movies in your area. Find out now: http://au.movies.yahoo.com/session-times/
-- 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.
