You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Dave Thompson (Jira)" <ji...@apache.org> on 2022/03/18 11:46:00 UTC

[jira] [Closed] (DAFFODIL-2655) Modify release candidate container to work for both daffodil and daffodil-vscode

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

Dave Thompson closed DAFFODIL-2655.
-----------------------------------

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

Verified changes identified in commit comments were implemented.

Release candidates for both daffodil and daffodil-vscode have been successfully generated.

> 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)