You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2007/06/16 02:12:26 UTC
[jira] Assigned: (DERBY-2832) things noticed broken in release
process.
[ https://issues.apache.org/jira/browse/DERBY-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren reassigned DERBY-2832:
-----------------------------------------
Assignee: Myrna van Lunteren
> 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.