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 pe
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.
I think you were right about the permissions -- Craig deployed the
1.0.3 artifacts and they are not
Yes we should be branching for releases in the future. Its a pain but
it prevents some of the mishaps that I've experienced the past two
days.
Sean
On 8/21/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 8/21/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
> Everything seems to be builidng correct
+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
a
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 ni
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* se
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?
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.
Yes its deploying most artifacts. The examples aren't being deployed
though so my suggestion is to simplify your sc
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
> no
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 f
* Bulk change of issues tagged 1.0.3-SNAPSHOT to 1.0.3, turning off email
notification
Yes this is the right approach. Turn off bulk email in Step 3 of the
bulk change. *Very* nice new JIRA feature.
* Remove the old 1.0.3-SNAPSHOT version.
Archive instead of delete.
Craig
Sean
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.) Sea
If you have tried out the dialog manager feature of Shale, you're probably
well aware that it has some limitations and bugs. Indeed, I see improving
this as the most important thing to tackle next. In reviewing the
outstanding bug reports, it looks like we will need to rearchitect the
current im
13 matches
Mail list logo
