2 days ago...
"hxp" wrote : It's been months since RC1; and you've been doing architecture surgery and feature additions up until just a few days ago. | | So please do a clean RC2 , post a binary for download... as well as leaving a stable CVS snapshot (see start of this thread).... | | ...and give us users at least 3-4 days to really do a good QA testing before putting out a final 1.0 release. | | You're getting really close, congrats, and thanks for all the good work! "cooper" wrote : yes this is my idea, a pre 1.0 will be done and will be put online on jboss.org as well to have a good q/a Julien, Why the switch? Why no RC2? With all the CVS build problems in the past few days, it's been hard for even dedicated users like me to do much deeper QA. I've got a list of bugs that you may (or may not) have fixed, but I didn't want to file bug reports until I'd done regression tests against the latest snapshot. javab0y wrote : Here is my suggestion...that the heads of this project utilize some of the features of CVS to provide for a workable checkout via branching/freezing code. Then have an unstable branch for the latest and greatest. This way nobody can complain if code does not work. Also...enforce the rule...if it doesn't compile..it should not be checked in...period. This is the way many open source projects run. If Nukes could do this, it would likely cut down on the amount of posts regarding execution and build issues. cooper wrote : you ae right, this is going to be done, ... | A 1.0 branch will be created soon as well. But on http://www.jboss.org/index.html?module=bb&op=viewtopic&t=46416 cooper wrote : the cvs has been tagged as Nukes_1_0, for now we don't branch. Out here in the troups, we need to get a better idea of what is going on in your mind and in your planning ;-) Otherwise, a lot of our attempts to help become largely (or completely) wasted. One idea: how about a cleaned-up and QA'ed 1.0.1 release in about a week or so? (Posted properly, with a fresh date, on Sourceforge, along with with an archived matching CVS-snapshot for those who want to go to the next deeper step of involvement.) This could also allow you to put off branching the CVS till 1.1, assuming 1.1 is no more than 1 month away. We need something that is both clean and stable, even if it doesnt have a lot of modules, that we can document around and use as a basis to help enlarge the team. I say the above constructively, with regard for all the hard work you've been putting into this, ...and congrats on getting it this far! -- Howard <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3824271#3824271";>View the original post</a> <a href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3824271>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
