FW: Castle 2.5.2 == 2.5.1?

10 views
Skip to first unread message

Paul Stovell

unread,
Feb 1, 2011, 8:58:12 PM2/1/11
to funnel...@googlegroups.com, dbup-d...@googlegroups.com, magellan...@googlegroups.com, krzyszto...@gmail.com
I just learnt an interesting approach to managing versioning dependencies problems from Krzysztof (see below). 

If we try to follow Semantic Versioning, breaking changes should only happen on major release versions, so we should be able to use the same idea to save recompilation. 

Paul
 

 

From: Krzysztof Kozmic
Sent: Wednesday, 2 February 2011 11:49 AM
To: Paul Stovell
Subject: RE: Castle 2.5.2 == 2.5.1?

 

For people who were whinging that with each minor bugfix release they have to recompile the whole world because everything depends on Windsor.

 

This is going to be the policy from now on, that Windsor will be versioned:

X.Y.0.0 for assembly version and

X.Y.A.B for file version where A is the minor release number and B is probably going to be either 0 or some number relating to revision.

HTH,

 

Krzysztof Koźmic

 

From: Paul Stovell
Sent: Wednesday, 2 February 2011 11:46 AM
To: Krzysztof Kozmic
Subject: Castle 2.5.2 == 2.5.1?

 

Hey KK,

 

http://sourceforge.net/projects/castleproject/files/Windsor/2.5/Castle.Windsor.2.5.2.zip/download

 

That ZIP file is for 2.5.2, but it has these attributes:

 

[assembly: AssemblyVersion("2.5.1.0")]

[assembly: AssemblyFileVersion("2.5.2.0")]

[assembly: AssemblyInformationalVersion("2.5.2.0")]

 

Out of curiosity, why keep the assembly version as 2.5.1?

 

Paul


Reply all
Reply to author
Forward
0 new messages