Hi Roelof,
I wouldn’t mind some help releasing it, no. Tonight I finished all
code + tests.
If you would
· pull from my Castle.Core clone and merge + release castle core 1.3
· Help me prepare the nant build file (only .sln builds right now)
· Help me update active record facility to match the new version of
Txs/AutoTx
I would really appreciate it.
I have tagged the finished code v2.0 on my git.
Henrik
*From:* [email protected]
[mailto:[email protected]] *On Behalf Of *Roelof Blom
*Sent:* den 9 mars 2010 09:38
*To:* [email protected]
*Subject:* Re: Git migration -
Castle.Facilities.AutomaticTransactionManagement
Hi,
I'd rather see a release of the Tx service, and for the two to stay
independent. Tx service taking a dependency on Windsor does not seem
right IMO.
Do you need any help with making a release?
-- Roelof.
On Tue, Mar 9, 2010 at 1:48 AM, Henrik Feldt <[email protected]
<mailto:[email protected]>> wrote:
What do you say about merging C.S.Tx and C.S.AutoTx? They are fairly
annoying to use on their own?
*From:* [email protected]
<mailto:[email protected]>
[mailto:[email protected]
<mailto:[email protected]>] *On Behalf Of *John Simons
*Sent:* den 1 mars 2010 01:31
*To:* [email protected]
<mailto:[email protected]>
*Subject:* Re: Git migration -
Castle.Facilities.AutomaticTransactionManagement
Yes, your assembly version should be 2.0.0, right?
but for subsequent patch releases then update only the fileversion.
Cheers
John
------------------------------------------------------------------------
*From:* Henrik Feldt <[email protected] <mailto:[email protected]>>
*To:* [email protected]
<mailto:[email protected]>
*Sent:* Mon, 1 March, 2010 11:28:01 AM
*Subject:* RE: Git migration -
Castle.Facilities.AutomaticTransactionManagement
About file versioning:
I'm going to update the assembly version, too, as the public interfaces
change.
Regards,
Henrik
-----Original Message-----
From: [email protected]
<mailto:[email protected]>
[mailto:[email protected]
<mailto:[email protected]>] On Behalf Of John Simons
Sent: den 28 februari 2010 22:15
To: Castle Project Development List
Subject: Re: Git migration -
Castle.Facilities.AutomaticTransactionManagement
Henrik,
There is a release guide on the web site -
http://www.castleproject.org/community/releaseguide.html
I know that is svn specific and needs to be updated for git but the
steps required for a release are similar, so have a look at it :) And
if possible submit a patch to update the release guide to be git
specific.
> Question: If C.S.Tx has submodule C.Core, C.F.TxM as submodule C.S.Tx,
what
> C.Core submodule will C.F.TxM have?
Why are you mentioning submodules? The project dependencies are kept
in the lib folders.
Also, read this thread about assembly/file versioning so that is
easier to put out small fixes:
http://groups.google.com/group/castle-project-devel/browse_thread/thread/b34
987a9980b215b/ae484513bac9ce5b
Cheers
John
On Mar 1, 6:42 am, "Henrik Feldt" <[email protected]
<mailto:[email protected]>> wrote:
> I've tagged as 1.0.3, 1.0.4, not with submodules though. I'm also
going to
> state that only major releases x.0.0 will be ever be alpha/beta/RC/RTM
with
> me ;).
>
> Question: If C.S.Tx has submodule C.Core, C.F.TxM as submodule C.S.Tx,
what
> C.Core submodule will C.F.TxM have?
>
> From: [email protected]
<mailto:[email protected]>
> [mailto:[email protected]
<mailto:[email protected]>] On Behalf Of Henrik Feldt
> Sent: den 28 februari 2010 19:56
> To: [email protected]
<mailto:[email protected]>
> Subject: RE: Git migration -
> Castle.Facilities.AutomaticTransactionManagement
>
> I'm going to
>
> 1. Clone
>
> 2. Add github.com/haf/Castle.Core
<http://github.com/haf/Castle.Core> as a submodule to S.Tx and F.ATM.
>
> 3. Add github.com/haf/S.Tx <http://github.com/haf/S.Tx> as a
submodule to F.ATM
>
> 4. Tag it all as v1.0.3 (not RC) (not tagging core)
>
> 5. Add new code, write e-mail to this list when I got all my
code in
> it, tag it as 1.5 on my origin. Push.
>
> 6. Try and include the submodule in my own projects for ATM, if
this
> works, tag F.ATM and S.Tx together into a tag v2.0 RC
>
> 7. Test with my own project, perform updates. Push it. Create a
> working branch with Castle.Core 1.2.0's tag as well and tag this
> appropriately.
>
> 8. Fix any lingering problems, tag as v2.0.
>
> 9. Push to my origin (github.com/haf <http://github.com/haf>)
>
> 10. Edit the wiki to say it's released
>
> 11. Ask for someone with access to pull from my repository
>
> 12. Ask for someone with access to edit the release-list at
> castleproject.org <http://castleproject.org>
>
> 13. Complete documentation for the facility and normal transaction
> project.
>
> Tell me if there's anything missing.
>
> Henrik
>
> From: [email protected]
<mailto:[email protected]>
> [mailto:[email protected]
<mailto:[email protected]>] On Behalf Of Roelof Blom
> Sent: den 20 februari 2010 08:25
> To: [email protected]
<mailto:[email protected]>
> Subject: Git migration - Castle.Facilities.AutomaticTransactionManagement
>
> Hi,
>
> Castle.Facilities.AutomaticTransactionManagement
> <http://github.com/castleproject/Castle.Facilities.AutomaticTransactio...
> ement> has migrated to git.
>
> Please use this thread for feedback, indicate problems or ask questions
> about the migration.
>
> -- Roelof.
>
> --
> 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]
<mailto:[email protected]>.
> To unsubscribe from this group, send email to
> [email protected]
<mailto:[email protected]>.
> For more options, visit this group
athttp://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]
<mailto:[email protected]>.
> To unsubscribe from this group, send email to
> [email protected]
<mailto:[email protected]>.
> For more options, visit this group
athttp://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]
<mailto:[email protected]>.
To unsubscribe from this group, send email to
[email protected]
<mailto:[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]
<mailto:[email protected]>.
To unsubscribe from this group, send email to
[email protected]
<mailto:[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]
<mailto:[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]
<mailto:[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]
<mailto:[email protected]>.
To unsubscribe from this group, send email to
[email protected]
<mailto:[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.
