Don't panic, you get the idea, let me clarify what you point. 1. No RC2 because I want to avoid the linux syndroma, we have not released enough in the project life (for various reasons). It was time to get out the 1.0 and I think it is fairly stable, the site has been updated many times recently and it's good. I want to release more often, this is good for the project.
2. We don't touch the core except bug fixes and minor fixes that I will do. If there are enough to justify a 1.0.1 we will do it with the fixes, etc... What I call the core : | * nukes/nukes | * nukes/bb | * nukes/permission | That part must get only bug fixes or addition I control. 3. At the same time we revamp the other modules, so no need to touch the core. What I want to be done are all the other modules. Already Jae is working hard on the News module. What I want is : | * use of templates | * integrate security | * integrate indexing | By the time we finish modules, we get out 1.1, 1.2, etc... 4. There is an obvious need for a testsuite (and your point about QA is directly related to that). Unfortunately it is hard to test web-app so we need to work hard on that. 5. Bottom line, what I want you to get is that both task are separate, due to the clean separation of the module architecture. In addition they don't share the same code space : nukes/news, nukes/polls, nukes/adminmessages, etc... <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3824277#3824277";>View the original post</a> <a href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3824277>Reply to the post</a> ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
