Actually I've just re-read your question "how bringing some facilities to Windsor's repository will affect it negatively?" and I don't see any negative affects as long as the release of the facilities is still separate.
In MR I'm planning to have 3 release packages: - The core MVC framework (this will include Validation + Binder + Pagination + Core) - The AR extension (this includes AR + its dependencies that are not already included in main package) - The Windsor extension (this includes Windsor + its dependencies that are not already included in main package) BTW, there was a discussion a while ago about merging binder into MR (http://groups.google.com/group/castle-project-devel/browse_thread/ thread/432e826d2b94a27c/3ae1e1b117a0cfed), are we still good to do this? Also in the same discussion we talked about moving Pagination into MR, and there were 2 people opposed, is this still a no go? Cheers John On Sep 22, 5:02 pm, Krzysztof Koźmic <[email protected]> wrote: > Why would they update if all that's changed is a facility they don't even > use? > > 2010/9/22 John Simons <[email protected]> > > > Here is a reason, a bug in any of those facilities requires a whole release > > of Windsor, which means an update to all Windsor users even if they do not > > use the affected facility. > > I think that is not user friendly at all. > > > Cheers > > John > > > ------------------------------ > > *From:* Krzysztof Koźmic <[email protected]> > > *To:* [email protected] > > *Sent:* Wed, 22 September, 2010 4:53:33 PM > > > *Subject:* Re: Projects release saga > > > I don't think we really can do anything about it. And since pretty much any > > other project depends on Core AND DynamicProxy or Dictionary Adapter (and > > not just within Castle) at least having single project to update instead of > > multiple means we have less work to do. > > > But anyway - we've diverged from the topic and main question, which was - > > how bringing some facilities to Windsor's repository will affect it > > negatively? > > > cheers, > > Krzysztof > > > 2010/9/22 Henry Conceição <[email protected]> > > >> Same here. > > >> Cheers, > >> Henry Conceição > > >> On Wed, Sep 22, 2010 at 2:17 AM, John Simons <[email protected]> > >> wrote: > >> > In my opinion Core is changing too much too frequently, and that is > >> because > >> > it has too much in it! > > >> > I don't have the magic answer, but I don't think packaging/merging as > >> many > >> > things together is the correct solution. > > >> > Cheers > >> > John > > >> > ________________________________ > >> > From: Henry Conceição <[email protected]> > >> > To: [email protected] > >> > Sent: Wed, 22 September, 2010 4:06:40 PM > >> > Subject: Re: Projects release saga > > >> > Mixed feelings. > > >> > It's easier for sure, but each time the Windsor and Core projects are > >> taking > >> > more burden hosting project's like these. The last release contains: > >> > core, windsor, microkernel, dynamicproxy, dictionary adapter and > >> > synchronize/event/startable/remoting/logging facilities. > > >> > Cheers, > >> > Henry Conceição > > >> > 2010/9/22 Krzysztof Koźmic <[email protected]>: > >> >> I'm just for merging projects where it makes sense. > >> >> And since stuff like ATM facility does not get much development anyway > >> >> it's > >> >> not really worth it to keep it separate. What do you think? > > >> >> 2010/9/22 Henry Conceição <[email protected]> > > >> >>> Well, at this pace will be back to old repo/single release model soon > >> ;-) > > >> >>> Cheers, > >> >>> Henry Conceição > > >> >>> 2010/9/22 Krzysztof Koźmic <[email protected]>: > >> >>> > ok, thanks! > > >> >>> > is there a reason NOT to keep some of the stuff outside of Windsor's > >> >>> > repository/project? > > >> >>> > That way we would release them together with Windsor and managing > >> them > >> >>> > would > >> >>> > be a bit easier (same like with Logging Facility and > >> >>> > SynchronizeFacility) > > >> >>> > 2010/9/22 Henry Conceição <[email protected]> > > >> >>> >> Not the validator assembly itself, but the validator tests projects > >> >>> >> have. > > >> >>> >> I did update most of them today, only monorail and ar facility are > >> >>> >> pending. > > >> >>> >> Cheers, > >> >>> >> Henry Conceição > > >> >>> >> 2010/9/22 Krzysztof Koźmic <[email protected]>: > >> >>> >> > Does validator have dependency on Core? > > >> >>> >> > 2010/9/22 Henry Conceição <[email protected]> > > >> >>> >> >> The AR Facility is, but to update it, you must start the path > >> from > >> >>> >> >> NHibernate.ByteCode provider, Validator, AR, Services > >> Transaction, > >> >>> >> >> ATM > >> >>> >> >> facility and them AR Facility. > > >> >>> >> >> And following the logic of release each project, you can't > >> release > >> >>> >> >> the > >> >>> >> >> AR Facility before the release of Validator, AR, Services TX and > >> >>> >> >> ATM. > > >> >>> >> >> Cheers, > >> >>> >> >> Henry Conceição > > >> >>> >> >> On Wed, Sep 22, 2010 at 1:41 AM, John Simons > >> >>> >> >> <[email protected]> > >> >>> >> >> wrote: > >> >>> >> >> > Yes that's right. > >> >>> >> >> > But at the moment these integration projects are not separate > >> and > >> >>> >> >> > I > >> >>> >> >> > think > >> >>> >> >> > they need to be for this to work! > > >> >>> >> >> > Yes I agree, the integration projects need to stand on their > >> own. > > >> >>> >> >> > John > > >> >>> >> >> > ________________________________ > >> >>> >> >> > From: Krzysztof Koźmic <[email protected]> > >> >>> >> >> > To: [email protected] > >> >>> >> >> > Sent: Wed, 22 September, 2010 3:27:18 PM > >> >>> >> >> > Subject: Re: Projects release saga > > >> >>> >> >> > John - I think the proposed solution some time ago was that > >> >>> >> >> > whoever > >> >>> >> >> > releases > >> >>> >> >> > one of the major projects (Windsor, AR, MR) should also update > >> >>> >> >> > integration > >> >>> >> >> > projects for the other projects. > > >> >>> >> >> > As such I will look at updating MR integration and AR > >> integration > >> >>> >> >> > today. > >> >>> >> >> > We > >> >>> >> >> > should also make these projects more visible so that it's easy > >> to > >> >>> >> >> > find > >> >>> >> >> > them > >> >>> >> >> > when someone needs them. > > >> >>> >> >> > W dniu 22 września 2010 15:25 użytkownik Krzysztof Koźmic > >> >>> >> >> > <[email protected]> napisał: > > >> >>> >> >> >> We should also have a serious look at automating as much of > >> the > >> >>> >> >> >> process > >> >>> >> >> >> as > >> >>> >> >> >> possible. It still is a PITA and requires too much manual > >> error > >> >>> >> >> >> prone > >> >>> >> >> >> work. > > >> >>> >> >> >> 2010/9/22 Henry Conceição <[email protected]> > > >> >>> >> >> >>> That we not do an official release (branching, uploading > >> >>> >> >> >>> packages, > >> >>> >> >> >>> and > >> >>> >> >> >>> the process that you described some time aga) for the small > >> >>> >> >> >>> projects > >> >>> >> >> >>> (validator, binder, etc). Just include the binaries on the > >> >>> >> >> >>> Monorail > >> >>> >> >> >>> package, and maybe pin the builds or create a branch. > > >> >>> >> >> >>> Cheers, > >> >>> >> >> >>> Henry Conceição > > >> >>> >> >> >>> 2010/9/22 Krzysztof Koźmic <[email protected]>: > >> >>> >> >> >>> > What do you mean > >> >>> >> >> >>> >> do we need to release the small projects? > > >> >>> >> >> >>> > ? > > >> >>> >> >> >>> > 2010/9/22 Henry Conceição <[email protected]> > > >> >>> >> >> >>> >> On the windsor release thread, John asked: > > >> >>> >> >> >>> >> "Are all MR dependencies going to have an official > >> release > >> >>> >> >> >>> >> compiled > >> >>> >> >> >>> >> against 2.5 ?" > > >> >>> >> >> >>> >> I was thinking about that and another question came to > >> me: > >> >>> >> >> >>> >> do > >> >>> >> >> >>> >> we > >> >>> >> >> >>> >> need > >> >>> >> >> >>> >> to release the small projects? Can't we only release the > >> top > >> >>> >> >> >>> >> projects? > > >> >>> >> >> >>> >> Cheers, > >> >>> >> >> >>> >> Henry Conceição > > >> >>> >> >> >>> >> -- > >> >>> >> >> >>> >> 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]<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]<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]<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 > > ... > > 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.
