Hi all,
I'm slowly getting the projects after migration cleaned up.
*Core*
project should be now all in good shape. As I plan to make a release
as soon as I clean this all up (and integrate one outstanding feature),
I have some questions that need to be answered - Which of those projects
we want to re-release and which versions they should have?
/As a reminder/, we now have in addition to what used to be there: [in
square brackets last released version] (in normal brackets suggested
version for the new release)
- Castle.Components.Binder [none] (3.0 / not release?)
- Castle.Components.Pagination [1.1.1] (3.0 / not release?)
- Castle.Components.Validator [2.5] (3.0 / not release?)
Core and logging services is a no-brainer, I'm not sure how to proceed
with the other ones. Also since Pagination is just a few types really,
perhaps we should make it a source-only release?
*Windsor*
This one I just started and it's more complicated.
We have the following new additions:
- Castle.Facilities.ActiveRecordIntegration [1.1.2RC] (3.0)
- Castle.Facilities.NHibernateIntegration [none] (3.0)
The problem with those is dependency on ActiveRecord and NHibernate.
Which versions of those dependencies do we want to have?
I'm pretty convinced NHibernate Facility should be built on top of
NHibernate 3.2.
Not too sure about ActiveRecord Facility. The last release was against
AR 3.0RC and NHibernate 3.1 Do we want to stick to those versions? What
is final AR going to be released against? NH 3.1 or 3.2? Also what is
the planned release schedule for AR and who is maintaining it these days?
AR Facility also has a dependency on Transaction Services. Henrik, what
are your plans for release against Core 3.0? Due to this dependency
release of this facility will need to be coordinated between Core,
Windsor, Active Record and Transactions. I can already feel the pain in
my ass.
*Nuget*
To alleviate some of the pain in maintaining all of this, I would like
to start using Nuget to manage our external depdendencies (NHibernate,
log4net, nlog etc). Any objections/suggestions relating that? +1 ? -1 ?
*Build Server*
The build server has recently tendency to go offline for multiple hours
at a time to do 'database cleanup'. This is extremely annoying.
Henry/Hammett can one of you guys have a look at what we can do to make
it stop/take significantly less time?
cheers,
Krzysztof
--
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.
