Okay, boys and girls: Let's get ready for the release! First of all, in case you missed it: I now have full access to the RubyForge project and why's repo at GitHub. I guess this makes me some sort of a project leader, but don't worry: The community will still maintain Camping. I will continue pushing to my own repo and will ask the mailing list before merging any big changes. Everything will still be maintained through this mailing list. I'm not going to work on any new features (not many, but I still have some ideas left); just preparing for this release. This means (in no specific order):
* Update the documentation * Update the GitHub wiki * Update the changelog * Clean up the examples * Choose a bug tracker * Write an announcement * Fix any bugs discovered while we're cleaning up I'm working on the documentation at the moment. I'm also going to take some of the essential stuff that was on the old wiki and put it right into the RDoc. The RDoc tempate (flipbook) is currently on hold until Eric Hodel finishes his awesome refactoring of RDoc. Then I'll convert it to the new template system and probably add search. When it comes to bug tracking, I really like ditz (http://ditz.rubyforge.org) + sheila (written in Camping; example: http://masanjin.net:9000/). What do you think? 2.0 will then be release, 2.0.x for minor fixes, 2.0.x.REV for bleeding edge (from my gem server) and 2.1 for completely new featues. Any comments or thoughts? Anyone else who want to do some of these things? Remember, I'm not _why ;-) //Magnus Holm
_______________________________________________ Camping-list mailing list [email protected] http://rubyforge.org/mailman/listinfo/camping-list
