Re: Nightly build problem
Everything seems to be builidng correctly now. Initially I was also having trouble building locally so I think it was an issue with ibiblio. Sean On 8/20/06, Sean Schofield [EMAIL PROTECTED] wrote: It seems like there is a problem with the nightly builds[1.] From the logs it looks like a permissions issue. I will investigate when I get a chance. Sean [1] http://myfaces.zones.apache.org:8080/continuum/servlet/continuum/target/Summary.vm/fid/continuumProject
Re: [VOTE] Shale Version 1.0.3 Release
+1 (Binding) On 8/20/06, Craig McClanahan [EMAIL PROTECTED] wrote: At long last :-), the bits are ready for a vote. All of the following files have md5 and sha1 checksums, and are in addition signed by my code signing key. They correspond to revision 433108 in the SVN repository, which I'm about to tag as APACHE_SHALE_1_0_3. (1) Maven Snapshot Repository At Apache: (http://people.apache.org/repo/m2-snapshot-repository) org.apache.shale.extras:mailreader-jpa:1.0.3 org.apache.shale:shale-apps-parent:1.0.3 org.apache.shale:shale-clay:1.0.3 org.apache.shale:shale-core:1.0.3 org.apache.shale:shale-dist:1.0.3 org.apache.shale:shale-parent:1.0.3 org.apache.shale:shale-remoting:1.0.3 org.apache.shale:shale-spring:1.0.3 org.apache.shale:shale-test:1.0.3 org.apache.shale:shale-tiger:1.0.3 org.apache.shale:shale-tiles:1.0.3 (If you have tested previous test builds of 1.0.3, you'll need to clear your local m2 repository to pick up these bits) (2) Release Artifacts (http://people.apache.org/~craigmcc/shale-proposed-release-1.0.3/) mailreader-jpa-1.0.3.zip shale-blank-1.0.3.zip shale-clay-usecases-1.0.3.zip shale-framework-1.0.3.zip shale-mailreader-1.0.3.zip shale-mailreader-jpa-1.0.3.zip shale-sql-browser-1.0.3.zip shale-usecases-1.0.3.zip (3) Vote Please review these artifacts, and test their signatures, then vote on whether we should release them as Apache Shale version 1.0.3. If it passes we'll hold a quality vote later on. [ ] +1 (Binding) for PMC members only [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released My vote is +1 (Binding) Craig McClanahan
Re: Nightly build problem
On 8/21/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 8/21/06, Sean Schofield [EMAIL PROTECTED] wrote: Everything seems to be builidng correctly now. Initially I was also having trouble building locally so I think it was an issue with ibiblio. Sean, is Continuum actually deploying nightly builds of Shale? I ask because I've also got a nightly cron job on the zones machine that does this. We don't need both, certainly. I think you were right about the permissions -- Craig deployed the 1.0.3 artifacts and they are not group writeable. Continuum would not have been able to overwrite them in the snapshot repo. Oops ... my nightly build script goes back and fixes things, and I forgot to do this on the manually deployed 1.0.3 stuff. Now that the POMs are updated (to 1.0.4-SNAPSHOT) I'll go fix the 1.0.3 things. Which is a *good* thing in this case, but something to consider for the future. With a CI server running, we may need to branch for releases. Yah, I shot myself in the foot on this one as well. -- Wendy Craig
Handling JIRA issues tagged with 1.0.3-SNAPSHOT
In order to wrap up the 1.0.3 release (which now has the three binding votes it needs to get out the door, but we'll leave things open a little while for any showstoppers), I want to clean up the JIRA issues that are currently tagged with 1.0.3-SNAPSHOT, changing that to 1.0.3 ... but *without* sending out scads of email. Is the following the right approach? * Create a new version 1.0.3 * Bulk change of issues tagged 1.0.3-SNAPSHOT to 1.0.3, turning off email notification * Remove the old 1.0.3-SNAPSHOT version. Craig PS: I see that I didn't publish the release notes yet either ... that'll happen tonight.
Re: Handling JIRA issues tagged with 1.0.3-SNAPSHOT
On 8/21/06, Craig McClanahan [EMAIL PROTECTED] wrote: * Create a new version 1.0.3 * Bulk change of issues tagged 1.0.3-SNAPSHOT to 1.0.3, turning off email notification * Remove the old 1.0.3-SNAPSHOT version. I think you can just change the description of 1.0.3-SNAPSHOT to 1.0.3. Sean? -- Wendy
Re: Handling JIRA issues tagged with 1.0.3-SNAPSHOT
I'll take care of this and update the wiki with the steps necessary. Sean On 8/21/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 8/21/06, Craig McClanahan [EMAIL PROTECTED] wrote: * Create a new version 1.0.3 * Bulk change of issues tagged 1.0.3-SNAPSHOT to 1.0.3, turning off email notification * Remove the old 1.0.3-SNAPSHOT version. I think you can just change the description of 1.0.3-SNAPSHOT to 1.0.3. Sean? -- Wendy
Re: Handling JIRA issues tagged with 1.0.3-SNAPSHOT
I took care of everything. Here are the steps for our future release template wiki. NOTE: We still need a meaningful description and release date for the new 1.0.3 version. 1.) Create a new JIRA version for the release (ex. 1.0.3) 2.) Search and then bulk change unresolved issues with a fix for of the old snapshot version (ex. 1.0.3-SNAPSHOT) and change to Unknown. At this point in the process, there shouldn't be any issues left on the roadmap but do a search (and bulk change) if necessary. For all bulk changes be sure to uncheck the Send mail for this update option on Step 3. 3.) Search and then bulk change resolved issues with a fix for of the old snapshot version (ex. 1.0.3-SNAPSHOT) and change to the new version (ex. 1.0.3). For all bulk changes be sure to uncheck the Send mail for this update option on Step 3. 4.) Archive the old version. This allows you to still search on issues that were *reported* against a SNAPSHOT version yet it prevents you from reporting new issues against the SNAPSHOT. Sean On 8/21/06, Sean Schofield [EMAIL PROTECTED] wrote: I'll take care of this and update the wiki with the steps necessary. Sean On 8/21/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 8/21/06, Craig McClanahan [EMAIL PROTECTED] wrote: * Create a new version 1.0.3 * Bulk change of issues tagged 1.0.3-SNAPSHOT to 1.0.3, turning off email notification * Remove the old 1.0.3-SNAPSHOT version. I think you can just change the description of 1.0.3-SNAPSHOT to 1.0.3. Sean? -- Wendy
Re: Handling JIRA issues tagged with 1.0.3-SNAPSHOT
On 8/21/06, Sean Schofield [EMAIL PROTECTED] wrote: I took care of everything. Here are the steps for our future release template wiki. NOTE: We still need a meaningful description and release date for the new 1.0.3 version. 1.) Create a new JIRA version for the release (ex. 1.0.3) 2.) Search and then bulk change unresolved issues with a fix for of the old snapshot version (ex. 1.0.3-SNAPSHOT) and change to Unknown. At this point in the process, there shouldn't be any issues left on the roadmap but do a search (and bulk change) if necessary. For all bulk changes be sure to uncheck the Send mail for this update option on Step 3. 3.) Search and then bulk change resolved issues with a fix for of the old snapshot version (ex. 1.0.3-SNAPSHOT) and change to the new version (ex. 1.0.3). For all bulk changes be sure to uncheck the Send mail for this update option on Step 3. Isn't this the same set of issues you just changed to Unknown in step 2? If so, how do you find them again? Craig 4.) Archive the old version. This allows you to still search on issues that were *reported* against a SNAPSHOT version yet it prevents you from reporting new issues against the SNAPSHOT. Sean On 8/21/06, Sean Schofield [EMAIL PROTECTED] wrote: I'll take care of this and update the wiki with the steps necessary. Sean On 8/21/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 8/21/06, Craig McClanahan [EMAIL PROTECTED] wrote: * Create a new version 1.0.3 * Bulk change of issues tagged 1.0.3-SNAPSHOT to 1.0.3, turning off email notification * Remove the old 1.0.3-SNAPSHOT version. I think you can just change the description of 1.0.3-SNAPSHOT to 1.0.3 . Sean? -- Wendy
