Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <32719307.1182291746083.JavaMail.jira@brutus>
Date: Tue, 19 Jun 2007 15:22:26 -0700 (PDT)
From: "Myrna van Lunteren (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-2832) things noticed broken in release
 process.
In-Reply-To: <5392571.1181944285862.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Myrna van Lunteren commented on DERBY-2832:
-------------------------------------------

On rereading the derbysnapshotorrelease page, I see it says *remove* the sane property. I set it to false. So, that bit is pilot error.

There already is a note indicating the maintversionprops2 does not handle the beta flag...
There are a number of bugs regarding the build failures with dita with the docs.
So that's all ok.
I made some small changes to the wiki.
I think this issue can be closed.

> things noticed broken in release process.
> -----------------------------------------
>
>                 Key: DERBY-2832
>                 URL: https://issues.apache.org/jira/browse/DERBY-2832
>             Project: Derby
>          Issue Type: Bug
>          Components: Build tools
>    Affects Versions: 10.3.1.0
>            Reporter: Myrna van Lunteren
>            Assignee: Myrna van Lunteren
>            Priority: Trivial
>
> This is a place holder for any issues I might run into.
> First:
> - add to wiki that it's important to ant clobber before attempting to build with an updated release.properties
> - org.apache.derbyBuild.maintversion2props has some issues re updating masters
>    - does not find it necessary to update major version numbers (i.e. I tried to use it for main, for updating from 10.3 to 10.4, and it just never updated any masters)
>    - does not find it necessary to update a flag  (beta/alpha) (i.e. I tried to use it for the branch, updating from 10.3.0.0 alpha to 10.3.1.0 beta, and it updated the masters to 10.3.1.0 alpha)
>    - is dependent on tools/release/build.xml having an up-to-date list of masters
> - jira: one jira issue was closed, but still showed up on the 10.3 open issues. However, I could not bulk-edit it.

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