<br><div><span class="gmail_quote">On 10/12/06, <b class="gmail_sendername">Max Rydahl Andersen</b> <<a href="mailto:max.andersen@jboss.com">max.andersen@jboss.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>2) <a href="http://sourceforge.net/project/showfiles.php?group_id=22866">http://sourceforge.net/project/showfiles.php?group_id=22866</a> says that<br>the "others" MD5 etc. is the last release ? :(</blockquote>
<div><br>Yeah, this is a sourceforge bug. The order of these releases is based on which one is the last one to be made, and there is no way to explicitly order them. I realized this after I created the first 2.0.0.Beta2 release (before others/no deps), and since there is no way to delete a package (only hide one), it is impossible to get around :(
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">3) Instead of writing "no dependencies" on<br><a href="http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=72248">
http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=72248</a><br>couldn't we write "No dependencies included" to reduce the confusion.</blockquote><div><br> Sure, done.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
4) <a href="http://labs.jboss.com/portal/jbosside/download/index.html">http://labs.jboss.com/portal/jbosside/download/index.html</a> should have a<br>comment about what nodeps mean</blockquote><div><br>Yup I planned on adding more 'descriptive' text to help the user.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">5) What took so long about getting this release out ? (I relased beta8 for<br>
this release 20 days ago) What can we do to prevent that for the next<br>release ?</blockquote><div><br>Well we had a rogue member who shall rename nameless refuse to update his feature.xml for a little while ;). Besides that, we had a few hick ups in our integration builds WRT JBossWS and JBossAS tools that took a week or so to solve, and also there were a few bumps with the new firstrun wizard, and a few bugs that needed ironing out with our new branding plugin and the "release" part of the build system as well. I think the best thing we can do to resolve this in the future would be to be as quick as possible with testing/bug fixing on our integration builds, and getting N&Ns, tags, and versioning info, to me in a timely manner also. Also, waiting until the last minute to debate a build-specific issue should be avoided.. if any of us have problems with a resolution we make in a team meeting/email in the future it would probably be best if we brought it up either at the meeting or as soon as possible afterwards so we don't hold up the release process.
<br></div></div><br>-- <br>Marshall Culpepper<br><a href="mailto:marshall.culpepper@jboss.com">marshall.culpepper@jboss.com</a><br>JBossIDE Team Lead<br>JBoss, a division of Red Hat