Sharp Architecture 2.0: How are we going to get there?

by alec.whittington 11. October 2010 06:14

Now that we have published our 2.0 road map, several people have asked us how are we going to get there. Simple, one step at a time.

One step at a time

We have previously blogged about Templify (here and here) being the way we are going to deliver a S#arp Architecture solution. That was step one for us, so you could say that we are already starting to deliver 2.0. Our next steps will be as follows (subject to change)

  1. Create an initial 2.0 release that includes (v1.7.X)
    1. Convert solution and projects to Visual Studio 2010
    2. Convert all projects to .NET 4.0
    3. Reorganize the solution structure for the solution template (moving to a Who Can Help Me based folder structure)
    4. Solution to use new MSBUILD based build system
    5. Package for Templify
    6. Document new Build process
    7. Add documents for Templify
  2. Create next release that includes (v1.8.X)
    1. LINQ Specifications
    2. Component composition
    3. Component registration
    4. Isolate NHibernate
  3. Create the next release (v1.8.5.X)
    1. Support for Castle 2.5
    2. Support for NH 3.0 (whether it is a GA release or not)
    3. Fluent NHiberate compiled against NH 3.0
    4. Support for MVC 3
    5. Change Validation (Data Annotations for UI, NHibernate.Validator for Model)
  4. Create the next release (v1.9.X)
    1. Convert Default Package to use Spark as its default view engine
    2. Add documentation (blogs and wiki) on how to properly setup the Spark environment
    3. Include the new Plugin architecture
    4. Add documentation (blogs and wiki) on the new Plugin architecture
    5. Support for NoRM / MongoDb
    6. Support for Azure
  5. Create the 2.0 release (v2.0.X)
    1. Final bug fixes
    2. Update all documentation
    3. Add samples via Blog posts
    4. Update Northwind
    5. Update Who Can Help Me
    6. Start creation of 3rd sample

All of this is subject to change based on the needs of the community / the team.

Conclusion

As you can see, we have an ambitious schedule a head of us. The team and I are really excited about what we have planned and cannot wait to share it with everyone. Some of it is very exciting, like the Plugin architecture and alternate data store support.

S#arp Architecture 1.6.5 will be the last stable release until 2.0 is released. The interim releases will all be listed as Alphas or Betas and should only be used in production if YOU are comfortable with it. If you are not or need to wait for a stable release, please wait for 2.0. For each release, we will also provide another Templify package. If you want the full source, you can download it from GitHub.

Tags: , , , , ,

Road Map | S#arp Architecture | Templify

Comments

10/11/2010 6:55:35 AM #

trackback

Sharp Architecture 2.0: How are we going to get there?

You've been kicked (a good thing) - Trackback from DotNetKicks.com

DotNetKicks.com |

10/11/2010 9:06:01 AM #

curlyfro

awesome!

thanks for the update Alec

curlyfro United States |

10/11/2010 10:48:29 AM #

todd brooks

Alec,

Thanks for the expanded roadmap update.  The roadmap is ambitious!  Looks great.

If a project is started with the 1.7x release, will it be possible to "upgrade" the project to each of the subsequent roadmap releases?   (Not necessarily an automated upgrade process, but a relatively painless upgrade path?)

Also, is there a rough, ballpark time schedule....Are we looking at 4 months for each "release"?  more/less?  Since this is a volunteer effort, I am not expecting you to commit to a time schedule, I'm just wondering if you have any kind of feel for these releases.

todd brooks United States |

10/11/2010 12:51:21 PM #

alec.whittington

Todd - There should only be minimal issues when upgrading from 1.7 to 2.0. The problem area I see is the 1.8.5 release with it's updated dependencies.

As far as time goes, I would like to see the complete release done within 4 months. Whether we can pull that off or not will remain to be seen. We are currently talking internally about how to best open some of these tasks up to the community. With the expanded abilities of the GitHub organization changes, this would allow us to give expanded access to certain users.

I will soon be posting on the google group a request for others that might be interested in actively being apart of the S# team. This might be in the roll of documentation, blog posting, bug fixes to current code base, etc.

alec.whittington United States |

10/11/2010 5:47:44 PM #

jack miao

thanks alec.
I am learning s#arp now

jack miao People's Republic of China |

Comments are closed

About the Team

Sharp Architecture was originally created by Billy McCafferty.

The project is currently led by Alec Whittington and the development team currently consists of James Broome, Jon George and Howard van Rooijen

Page List