1 matthius Mar 15, 2005 03:21
3 matthius Mar 15, 2005 21:36
Thank you for your quick response. I understand the risks and nature of the CVS version I'm not an official dev for this project but I'm willing to contribute. Is there a place I should post bugs such as this or workarounds I come up with?
- Matt
EdB wrote:
From the downloads page:
You can also get the absolute latest cutting edge (and thus potentially untested and unstable) version of b2evo from the CVS sever on SourceForge.net. There is absolutely no guarantee about the state of the CVS version. Some days it will be the most stable version you could find, and some days it might just be broken and waiting for a fix... This version is only recommended for contributing developers.
If you want to play with CVS and you use it on a production blog you do so at your own risk. I run a CVS installation just to see what the future holds, but it is NOT a real blog and gets wiped out frequently.
4 graham Mar 15, 2005 23:20
Post them in this forum. If you're really interested in joining the dev team email Francois and he'll set you up with all the mailing lists and stuff.
From the downloads page:
If you want to play with CVS and you use it on a production blog you do so at your own risk. I run a CVS installation just to see what the future holds, but it is NOT a real blog and gets wiped out frequently.