[ 
https://issues.apache.org/jira/browse/DAFFODIL-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Thompson closed DAFFODIL-2495.
-----------------------------------

Verified the specified commit (commit d9e2839b7fda1bcdd259d6a0915d1f4abda348d4) 
is included in the latest pull from the daffodil repository.

Verified changes by code review.

> Need way to dry-run release candidates from repos/branches other than 
> apache/daffodil@master
> --------------------------------------------------------------------------------------------
>
>                 Key: DAFFODIL-2495
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2495
>             Project: Daffodil
>          Issue Type: Bug
>            Reporter: Steve Lawrence
>            Assignee: Steve Lawrence
>            Priority: Major
>             Fix For: 3.1.0
>
>
> One of the tests that is useful to perform is a --dry-run of the release 
> candidate script. However, this currently always pulls from that master 
> branch of the apache/daffodil repo. Sometimes it is useful to do that on a 
> different branch of a different repo before things are merged, such as with 
> pull requests.
> We should change the release candidate script so that you can specify an 
> alternative repo/branch when running a --dry-run. When not doing a dry-run, 
> it should still always build from apache/daffodil@master.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to