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

Steve Lawrence resolved DAFFODIL-2655.
--------------------------------------
    Fix Version/s: 3.3.0
       Resolution: Fixed

Fixed in commit 4c62cdf901848bbac03dce7316a248bf8b8f0bbb

> Modify release candidate container to work for both daffodil and 
> daffodil-vscode
> --------------------------------------------------------------------------------
>
>                 Key: DAFFODIL-2655
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2655
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Infrastructure
>            Reporter: Steve Lawrence
>            Assignee: Steve Lawrence
>            Priority: Major
>             Fix For: 3.3.0
>
>
> The Daffodil release candidate container automates many of the complex steps 
> related to creating a release candidate. The majority of the steps are 
> exactly the same for both the daffodil repo and the daffodil-vscode repo, 
> except for a couple paths and build steps. We should modify the release 
> candidate container so that it can build either release candidate. 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to