On Fri, Oct 2, 2009 at 1:26 AM, Martin Cooper <mart...@apache.org> wrote: > On Thu, Oct 1, 2009 at 10:44 AM, Musachy Barroso <musa...@gmail.com> wrote: >> that sounds good to me. If we just overwrite 2.1.8 then the mirrors >> will also be updated right? This is technically speaking 2.1.8. > > The answer to that is "maybe". Some mirrors will update, others will > not. This is one of the main reasons that we do not publish another > build (or even part of it) with the same build number. > > As it seems we've decided later in the thread, we need to roll a new > version. Version numbers are free, after all. > > I agree with Wendy, too, that this next one needs more testing, to > make sure we don't run into these kinds of problems again. In fact, I > would ask those who voted on 2.1.8 to look at how they tested before > they voted, and perhaps think about ways in which they might change > their testing so that we can catch something like this before it goes > out in a release again.
Well, I did notice that the zips were malfunctioning (see my previous email), but I assumed it was a local problem (bad harddrive with many corrupted sectors), so I did test it on another machine where it worked fine. Of course, that other machine was a mac. How many devs are on Windows, anyways? - Phil > > -- > Martin Cooper > > >> musachy >> >> On Thu, Oct 1, 2009 at 10:30 AM, Wes Wannemacher <w...@wantii.com> wrote: >>> So, I was trying to figure out what is going on here because there are >>> more problems with the zip than mentioned on the user@ list. Since I >>> took site-deploy out of the release plugins default goals (to keep >>> other artifacts from stomping the main struts.apache.org site), it had >>> the unintended side effect of not running the site generation for the >>> rest of the artifacts... This means that (among other things) the >>> javadocs aren't in the docs zip. >>> >>> I am going to pull down the 2.1.8 sources via the tag and create a >>> 2.1.8.1 build to fix the docs zip. I will configure the release plugin >>> on the struts2 pom file (so that I will not be making changes to >>> struts-master). In addition, I will fix the funky characters in >>> filenames by passing the appropriate parameters to wget. To do this, I >>> will have to branch SVN, so I want to make a 2.1 branch and then we >>> can make this the time to move trunk to 2.2.0 and begin working on >>> some of the recent ideas (incorporating xwork being the biggest). >>> >>> >>> -- >>> Wes Wannemacher >>> >>> Head Engineer, WanTii, Inc. >>> Need Training? Struts, Spring, Maven, Tomcat... >>> Ask me for a quote! >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org >>> For additional commands, e-mail: dev-h...@struts.apache.org >>> >>> >> >> >> >> -- >> "Hey you! Would you help me to carry the stone?" Pink Floyd >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org >> For additional commands, e-mail: dev-h...@struts.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > > -- "We cannot change the cards we are dealt, just how we play the hand." - Randy Pausch --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
