DasBlog June 2007 Release
It's hard to run an Open Source project, not unlike herding cats. However, we've got an enthusiastic and involved team over on the DasBlog Developer mailing list, but sometimes we forget that even though there's been like 100 posts this week, most folks just look at the last release and figure, "oh, it's been 9 months, this project is dead." That's our fault. We should be releasing every month. (We do, we just don't package it up and put it on SourceForge - lame of us.) I give SubText credit for keeping their project moving along and feeling fresh.
We're still very actively working on DasBlog, and we're slowly getting our heads screwed on right. To be clear, the DasBlog 1.x codebase does support ASP.NET 1.1 and ASP.NET 2.0 as well. Currently, for June, here's what's going on:
10 June 2007 - Feature Complete for 1.x. No new features added after this point.
17 June 2007 - Last day for commits. Have patches for bugs submitted before this day.
18 June 2007 - Everyone who's interested should test the Daily Build we release as the final beta.
The bug bar for any check-ins after June 18 going forward should be:
- Bug breaks a major feature without any possible workaround
- Security issues
- Performance issues that would keep High Traffic Blogs from using the build
- Totally embarrassing low-impact bug (typos)
If all is good, this will be the final 1.1 compatible version, and the final 1.x release. The next release will be all 2.0, with the new version number being 2.x. We'll also aim for a release that runs under Medium Trust. Thanks to Clemens for kicking us in the tuckus.
About Scott
Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.
About Newsletter
do don't really believe that SQL makes upgrades easier, do you?
Clemens
If you spelunk the Subtext code, I have some very good support for upgrading database schemas. I even separated some of the code into a separate library: Subtext.Scripting. It's basically code that can execute templated sql queries.
What I really need is to get a license to the Red Gate tools. I end up spending a lot of time hand writing upgrade scripts to make sure their idempotent, so if you run the same scripts twice, nothing bad happens. At work, we do some interesting stuff to version SQL. I'll write about that in a future blog post.
Thanks for the big ups. :)
- be able to display archives in different ways. Having a blog dating back to 2003, I don't necessarily want everything more listed. Takes up real estate.
- Batch rename of Categories. Vasanth Dharmaraj at http://www.vasanth.in/ had a tool but it no longer works with the current version.
- Option to use SQL 2k5.
Thanks.
Yes, SQL is on our roadmap.
The current release includes some PowerShell scripts for Category Renaming/Adding/Deleting. It's VERY basic, and we're aware of the need to normalize Categories.
Or maybe something with the format below
2002 | 1 | 2 | 3 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12
---------------------------------------------------------
2004 | 1 | 2 | 3 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12
---------------------------------------------------------
2005 | 1 | 2 | 3 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12
---------------------------------------------------------
2006 | 1 | 2 | 3 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12
---------------------------------------------------------
There's no macro for the Google Search, just a custom blank HTML template. I suspose we could make a custom page for that to make it work out of the box...
Comments are closed.
Here's what I'd like to see go into future releases in the near future:
* Full 2.0 support (just casting my vote)
* The option to run dasBlog against SQL Server 2000/2005
* Easier upgrades (the above option will make it a LOT easier) -- this will also be useful when the updates are more frequent.
* Search comments, trackbacks, and pingbacks for keywords (spam). Then allow batch-deleting of such items.
I'm really trying to find the time to contribute to this project, so if anybody on the team wouldn't mind me putting them on MSN so I could bug you with questions I would appreciate it :).