On Mon, Jan 18, 2010 at 12:27 PM, Wendy Smoak <wsm...@gmail.com> wrote: > > (In the future the archetypes could be released together, it just puts > an additional burden on the RM to deal with extra artifacts and the > devs to test them in addition to the rest of the release. I would not > hold these up waiting for a struts-with-xwork release.) >
I agree with Wendy on both points here, but I will add that this is something that has a tendency to generate complaints. I, for one, am guilty of pushing out a traditional release and then forgetting about the archetypes.... I think this is part of why Lukasz is where he is at right now (sorry, buddy!). IMO, the argument of the testing being more difficult is somewhat debatable, because if the main artifacts are releasable quality, then it should be right around the corner that the active testers will then need to test the archetypes. So, to summarize, I say go with Wendy's suggestion to just start a new vote with the sigs attached, then we'll discuss how we proceed (struts 2.1.9 w/o xwork or struts 2.2.0 with xwork as our own artifact). -Wes -- 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
