Re: Struts 1.2.2 [was Patch to make sure ...]
That page says it is immutable. You are not allowed to edit this page. -- James Mitchell Software Engineer / Open Source Evangelist EdgeTech, Inc. 678.910.8017 AIM: jmitchtx - Original Message - From: Ted Husted [EMAIL PROTECTED] To: Struts Developers List [EMAIL PROTECTED] Sent: Wednesday, August 25, 2004 9:47 AM Subject: Re: Struts 1.2.2 [was Patch to make sure ...] No, I'm not running with the torch, I'm trying to pass the baton. :) If you (or anyone else) has run the Cactus tests since yesterday's code changes, please feel free to update the Wiki. * http://wiki.apache.org/struts/StrutsRelease122 Then we'd be down to play testing the bundled applications and Release Checklist steps A1-A6. -Ted. On Wed, 25 Aug 2004 08:59:06 -0400, James Mitchell wrote: Am I to assume the recent cvs activity to be what I think it means? I was just reading over the release instructions and was about to volunteer some time, but if you're running with the torch, I'll wait till next time. (besides, I would need some hand-holding for the first time anyway) Not sure if this help you, but I've already refreshed my local cvs and run the full gauntlet of tests and they all pass. I also ran the distribution without problems. (this was prior to your updating the docs) Anyway, let me know if I can help with anything else. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 1.2.2 [was Patch to make sure ...]
GREAT!!! I just removed the tag. Thanks for the help. I assume the wiki was incorrect. I'll update it. -- James Mitchell Software Engineer / Open Source Evangelist EdgeTech, Inc. 678.910.8017 AIM: jmitchtx - Original Message - From: Joe Germuska [EMAIL PROTECTED] To: Struts Developers List [EMAIL PROTECTED] Sent: Wednesday, August 25, 2004 2:22 PM Subject: Re: Struts 1.2.2 [was Patch to make sure ...] * I've tagged cvs with STRUTS_1_2_2 (from the wiki, or should that have been 1_1_2?) Either way, I've found a few items I want to update, can I remove or move the tag? Or just retag? You can do both. You can move a tag with: this will apply the tag to the versions you have currently checked out from CVS (presumably CVS HEAD) cvs tag -F STRUTS_1_2_2 this will remove the tag cvs tag -d STRUTS_1_2_2 this will apply the tag to CVS HEAD without any question cvs rtag -d $APACHE_CVSROOT -F STRUTS_1_2_2 jakarta-struts (you have to specify the CVSROOT in this case because rtag is not relative to any local sandbox) For the cvs tag commands, you can specify certain files or, by default, apply the command to all files in the current directory and subdirectories. Hope this helps. Thanks for taking the baton! Joe -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com In fact, when I die, if I don't hear 'A Love Supreme,' I'll turn back; I'll know I'm in the wrong place. - Carlos Santana - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 1.2.2 [was Patch to make sure ...]
On Wed, 25 Aug 2004 14:05:13 -0400, James Mitchell [EMAIL PROTECTED] wrote: Ok, I accept the challenge. If you could clarify something for me though: * IIRC, this release needs to be voted GA by our [committers/PMC] before we can announce the release as GA. Has that vote happened? No, not yet. * What is the status of the validator 1.1.3. Ted's entry in the wiki mirrors my own suspicion. Any clarity would help me here. The release doesn't appear on ibiblio, so we (commons folks) need to make that happen as well. It's effectively release. The distribution is up and the web site has been updated. I just need to send out the announcement (which I'll do today). * Do I need to close or mark 'later' all the bugs in bugzilla? Only if you feel like going back and reopening them all later. ;-) * I've tagged cvs with STRUTS_1_2_2 (from the wiki, or should that have been 1_1_2?) Either way, I've found a few items I want to update, can I remove or move the tag? Or just retag? Tagging HEAD as STRUTS_1_2_2 is right, I believe. Moving the tag on individual files is easy enough, assuming there aren't lots of them. See: https://www.cvshome.org/docs/manual/cvs-1.11.17/cvs_4.html#SEC51 -- Martin Cooper -- James Mitchell Software Engineer / Open Source Evangelist EdgeTech, Inc. 678.910.8017 AIM: jmitchtx - Original Message - From: Ted Husted [EMAIL PROTECTED] To: Struts Developers List [EMAIL PROTECTED] Sent: Wednesday, August 25, 2004 11:21 AM Subject: Re: Struts 1.2.2 [was Patch to make sure ...] Run with it, James. If anyone wants to pitch in, they can. But this doesn't have to be a one-person job. (Though there's not much to A1-A6.) Just keep the wiki page (that Niall started) updated. We are all jointly and severally responsible for Struts. Anyone can roll a release whenever they like. The only question is whether it will earn the Apache Struts brand through a majority vote (3 +1s, more +1s than -1s). The release plans and checklists are just a means to that end. -Ted. On Wed, 25 Aug 2004 10:55:58 -0400, James Mitchell wrote: Ok, I've finished testing the apps and all. What can I do now? Do you want me to take over and finish this? I though Niall or someone was working on it. Could be my bad memory, anyway, I'll do it if you guys don't mind me asking stupid 'release manager' newbie questions :P (and I'll keep it on-list for others who want to do it later). I'll even try to keep a log and throw a page on the wiki. -- James Mitchell Software Engineer / Open Source Evangelist EdgeTech, Inc. 678.910.8017 AIM: jmitchtx - Original Message - From: Ted Husted [EMAIL PROTECTED] To: Struts Developers List [EMAIL PROTECTED] Sent: Wednesday, August 25, 2004 9:47 AM Subject: Re: Struts 1.2.2 [was Patch to make sure ...] No, I'm not running with the torch, I'm trying to pass the baton. :) If you (or anyone else) has run the Cactus tests since yesterday's code changes, please feel free to update the Wiki. * http://wiki.apache.org/struts/StrutsRelease122 Then we'd be down to play testing the bundled applications and Release Checklist steps A1-A6. -Ted. On Wed, 25 Aug 2004 08:59:06 -0400, James Mitchell wrote: Am I to assume the recent cvs activity to be what I think it means? I was just reading over the release instructions and was about to volunteer some time, but if you're running with the torch, I'll wait till next time. (besides, I would need some hand-holding for the first time anyway) Not sure if this help you, but I've already refreshed my local cvs and run the full gauntlet of tests and they all pass. I also ran the distribution without problems. (this was prior to your updating the docs) Anyway, let me know if I can help with anything else. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 1.2.2 [was Patch to make sure ...]
On Wed, 25 Aug 2004 14:05:13 -0400, James Mitchell [EMAIL PROTECTED] wrote: Ok, I accept the challenge. If you could clarify something for me though: * IIRC, this release needs to be voted GA by our [committers/PMC] before we can announce the release as GA. Has that vote happened? No, not yet. Ok, I'll send out a vote. * What is the status of the validator 1.1.3. Ted's entry in the wiki mirrors my own suspicion. Any clarity would help me here. The release doesn't appear on ibiblio, so we (commons folks) need to make that happen as well. It's effectively release. The distribution is up and the web site has been updated. I just need to send out the announcement (which I'll do today). * Do I need to close or mark 'later' all the bugs in bugzilla? Only if you feel like going back and reopening them all later. ;-) Alrighty then, never mind. :D * I've tagged cvs with STRUTS_1_2_2 (from the wiki, or should that have been 1_1_2?) Either way, I've found a few items I want to update, can I remove or move the tag? Or just retag? Tagging HEAD as STRUTS_1_2_2 is right, I believe. Moving the tag on individual files is easy enough, assuming there aren't lots of them. I'll leave off the tag until I finish updating the docs. See: https://www.cvshome.org/docs/manual/cvs-1.11.17/cvs_4.html#SEC51 -- Martin Cooper -- James Mitchell Software Engineer / Open Source Evangelist EdgeTech, Inc. 678.910.8017 AIM: jmitchtx - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 1.2.2 [was Patch to make sure ...]
Also, I'm trying to get all the commit notes since 1.1. maven site:gen doesn't work for me. How do you guys do it? -- James Mitchell Software Engineer / Open Source Evangelist EdgeTech, Inc. 678.910.8017 AIM: jmitchtx - Original Message - From: James Mitchell [EMAIL PROTECTED] To: Struts Developers List [EMAIL PROTECTED] Sent: Wednesday, August 25, 2004 3:00 PM Subject: Re: Struts 1.2.2 [was Patch to make sure ...] On Wed, 25 Aug 2004 14:05:13 -0400, James Mitchell [EMAIL PROTECTED] wrote: Ok, I accept the challenge. If you could clarify something for me though: * IIRC, this release needs to be voted GA by our [committers/PMC] before we can announce the release as GA. Has that vote happened? No, not yet. Ok, I'll send out a vote. * What is the status of the validator 1.1.3. Ted's entry in the wiki mirrors my own suspicion. Any clarity would help me here. The release doesn't appear on ibiblio, so we (commons folks) need to make that happen as well. It's effectively release. The distribution is up and the web site has been updated. I just need to send out the announcement (which I'll do today). * Do I need to close or mark 'later' all the bugs in bugzilla? Only if you feel like going back and reopening them all later. ;-) Alrighty then, never mind. :D * I've tagged cvs with STRUTS_1_2_2 (from the wiki, or should that have been 1_1_2?) Either way, I've found a few items I want to update, can I remove or move the tag? Or just retag? Tagging HEAD as STRUTS_1_2_2 is right, I believe. Moving the tag on individual files is easy enough, assuming there aren't lots of them. I'll leave off the tag until I finish updating the docs. See: https://www.cvshome.org/docs/manual/cvs-1.11.17/cvs_4.html#SEC51 -- Martin Cooper -- James Mitchell Software Engineer / Open Source Evangelist EdgeTech, Inc. 678.910.8017 AIM: jmitchtx - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 1.2.2 [was Patch to make sure ...]
That should be cvs.apache.org:/www/cvs.apache.org/dist/struts/ So on the cvs.apache.org server, copy the distribution files to /www/cvs.apache.org/dist/struts/v1.2.2/. Since I was already in there, double-checking, I went ahead and made the directory. So, it's waiting for you :) And if there is still any controversy about the tag, we are in fact at release 1_2_2 Struts 1.1 was the first and last release in the 1.1.x series. The 1.2.0 release died on the vine. The 1.2.1 release was close, but no cigar. So, we're up to 1.2.2. -T. On Wed, 25 Aug 2004 15:26:05 -0400, James Mitchell wrote: Ok, A3 says to upload to /dist/struts, but there is nothing in /dist. Is that on purpose? Is that a staging area that some process polls and does something with it? Ok, I'm heading home to coach my kids soccer practice, and I'll be back on the horse after that. Thanks for your help -- James Mitchell Software Engineer / Open Source Evangelist EdgeTech, Inc. 678.910.8017 AIM: jmitchtx - Original Message - From: Ted Husted [EMAIL PROTECTED] To: Struts Developers List [EMAIL PROTECTED] Sent: Wednesday, August 25, 2004 3:11 PM Subject: Re: Struts 1.2.2 [was Patch to make sure ...] On Wed, 25 Aug 2004 15:00:07 -0400, James Mitchell wrote: Ok, I'll send out a vote. We can't vote on something that doesn't exist yet :) Go through A1 to A6 in the check list THEN call for the vote. The releases default to Alpha, and then we can grade it Beta or GA by majority vote. (Or downgrade it later, if we discover a buried issue.) Once it receives the GA stamp (which make take a few days), then we can do the second part of the release checklist. This is essentially the 1.2.1 release with some minor tweaks, so I would expect it to go GA quickly. -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
