File releases and branches.

Developer
Feb 26, 2010 at 10:35 AM

Would it make sense to make a binary file release, even if it is still an alpha stage?

Firstly: the idea is coming from my personal experience, when I 'm looking for libraries/tools/utilities I usually prefer to download binary files/installers/packages.

Secondly: it would be good to have some branches and tags. Including, file release tags, stable and experimental branches.

Feb 28, 2010 at 3:27 PM

Hi Sergey,

I think it would make sense. Having a binary release would make it easier for developers to use the software as they wouldn't have to install SVN, checkout and build.

Also, thanks for configuring the branches, tags and trunk in SVN.

Developer
Mar 1, 2010 at 5:45 PM

Ok, what is the version number should be?

Major.Minor.Build.Revision

IMHO:

  1. The release package name and a folder should contain the version number, may be not including a revision number. For example: linqtoxsd.1.0.0.zip
  2. Major.Minor, let the current version be 1.0.
  3. Build is a bug fix (currently 0).
  4. Revision is a SVN revision, for example 40139. I could make a small tool to generate the assembly.cs and zip/msi files.
  • Build is a big fix.
Mar 1, 2010 at 10:11 PM

That sounds fine. Thanks.