db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean T. Anderson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3264) track changes for release
Date Sat, 08 Dec 2007 01:02:43 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549627

Jean T. Anderson commented on DERBY-3264:

>From a structural viewpoint, the cgi file looks fine to me.

I appreciate that not being able to test the cgi before deploying it on people.a.o can be

For other extreme web site changes I have sometime copied build/site to a temp location locally,
removed all the files from build/site/binaries (to make the result smaller), then tar'd it
up and scp'd it to my public_html directory on people.a.o. So, if you want that extra measure
of security in this case, you might consider it.

But if the deployment goofs up, don't lose any sleep over it. there's plenty of opportunity
to correct it. In the meantime, people can always get to the latest archive release.

> track changes for release 
> -----------------------------------
>                 Key: DERBY-3264
>                 URL: https://issues.apache.org/jira/browse/DERBY-3264
>             Project: Derby
>          Issue Type: Task
>          Components: Web Site
>    Affects Versions:
>            Reporter: Kathey Marsden
>            Assignee: Kathey Marsden
>            Priority: Minor
>         Attachments: derby_3264_web_diff.txt
> Track changes for release. I probably should have created this earlier, but
making it now that I can post website patch.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message