Currently, the .NET Bio project exists in a single TFS branch, which makes maintenance trivial and simplifies versioning; as a project staffed by volunteers, simplicity is a distinct advantage – if we maintained multiple
branches, we would have to handle issues of synchronizing code updates across all active branches. Also, CodePlex source downloads always give you all branches, which can be unwieldy and confusing.
As the release dates for Visual Studio 2012 and .NET 4.5 come closer, we need to ensure compatibility with these new releases. My suggestion is:
We retain the single-branch approach in TFS
We wait until the new releases have been current for at least six months, to ensure stability and widespread usage
We generate a release, which will be the final version created with a requirement of VS2010/.NET 4.0 - this will be retained in the downloads for the foreseeable future.
We change our software requirements to VS2012/.NET 4.5, test compatibility and resolve any issues, then generate a new release matching the new requirements. This will become the recommended release.
I’d be very interested to get feedback from those using .NET Bio – would this work for you? If not, what do you see as the main problems and how would you like to see them addressed?