On Sun, Apr 26, 2009 at 4:27 PM, Wes Wannemacher <w...@wantii.com> wrote:
> On Sunday 26 April 2009 07:14:30 pm Martin Cooper wrote: > > On Sun, Apr 26, 2009 at 2:55 PM, Wes Wannemacher <w...@wantii.com> > wrote: > > > Which brings me back to my first question. Knowing that lukasz will be > > > added any day now, should we hold off a few days? Otherwise we will > > > all have to spin some cycles again on this for the next release. > > > > Is your concern that you want to get Lukasz in for the subsequent Struts > > release, or that you don't want to have to release the POM again? > > > > Technically, Lukasz is a committer now; he just doesn't have his account > > set up yet. So, even though we don't have the right 'id' and 'email' > > entries for the POM, you could still add him now, if you want. > > > > Either way, whenever Lukasz gets his account, we can update the POM and > > release it immediately. There's nothing that says we have to wait until > > we're holding up another Struts release before we release the POM again. > > ;-) > > > > No offense to Lukasz, just that I didn't want to go through the exercise of > voting on struts-master... Waiting 72 hours, releasing struts 2.1.7, > waiting > 72 hours... And then, going through the same thing again for 2.1.8 (or > whatever we release next... 2.0.15? 1.3.x whatever). There's no requirement to serialise votes and releases the way you describe above. In fact, as Wendy pointed out before, we could actually run the votes concurrently. I'd say there's very little chance that the POM vote would fail, so there would be little risk to that approach. Also, even if we went ahead and released the POM now, we could still release it again immediately after Lukasz's account is set up. No need to wait until we're close to another release. I'm not advocating any particular approach here - just clarifying the options. -- Martin Cooper > It's not that I'm impatient or against the voting process, but we know > there > is another change coming and I put forth the original push to get 2.1.7, so > I'm thinking a few more days now saves us a few days for the next release > (which could be time-constrained), then I'll let it happen. I think as soon > as > we know what his apache username is going to be, we can move forward. A > quick > check on people.a.o shows no evidence of him being added yet. Since there > are > at least a few fixes people are waiting on, if we don't know it in the next > day or so, we'll move forward. > > Of course, I am making a mental note that we have to get struts-master out > before other releases, so when I see changes, I'm likely to call a vote, > since > 1) it should be easy to test/release and 2) keeping on top of it will keep > us > from holding up future releases. Right now, in struts-master, there are > pending changes and it is a snapshot, so whether we move forward with 2.1.7 > or > not, it will still require a vote. So, I'm thinking Musachy is right, we > give > it a few days. > > -Wes > > > -- > > Wes Wannemacher > Author - Struts 2 In Practice > Includes coverage of Struts 2.1, Spring, JPA, JQuery, Sitemesh and more > http://www.manning.com/wannemacher > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > >
