Hi,
I see your point. I'll move it back into C.S.Tx then and make a pull request for .Core so that it can be placed in scm at least? When vNext then is released this has to be coordinated with C.S.Tx. I'll let you know when this is done. What about the other integration; C.F.AR-Integration? Cheers, Henrik From: [email protected] [mailto:[email protected]] On Behalf Of Roelof Blom Sent: den 10 mars 2010 15:02 To: [email protected] Subject: Re: Git migration - Castle.Facilities.AutomaticTransactionManagement Thanks for the lengthy email. IMO adding a public symbol is a breaking change. To be concrete: by adding the public interfaces and classes to Core 1.2 you'll break the contract. Sure existing code will compile with the new version, but code dependent on Core w/ new symbols will not work against "old" Core, even though the assembly versions are the same. Basically, we would have two versions 1.2 of Core. Confusing. I ask you to follow Krzysztof's earlier advice, and release the projects against the existing 1.2 Core. Then with all the reshuffling going on with Core vNext it can land there. -- Roelof. On Wed, Mar 10, 2010 at 2:21 PM, Roelof Blom <[email protected]> wrote: Cool, thanks. On Wed, Mar 10, 2010 at 1:38 PM, Henrik Feldt <[email protected]> wrote: I'm going to clarify this on another thread. Writing a longer e-mail now. From: [email protected] [mailto:[email protected]] On Behalf Of Roelof Blom Sent: den 10 mars 2010 13:31 To: [email protected] Subject: Re: Git migration - Castle.Facilities.AutomaticTransactionManagement I'm sorry but I really don't understand what your saying with 'the upgrade of the "coherent tree" of version blalblala". On Wed, Mar 10, 2010 at 12:51 PM, Henrik Feldt <[email protected]> wrote: Hi, I think it would be better to include the new namespace in core as the upgrade of the "coherent tree" of version should be made or should be fairly automatic or otherwise perhaps even made to happen now. What do you think? Henrik -- 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] <mailto:castle-project-devel%[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] <mailto:castle-project-devel%[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.
