You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@daffodil.apache.org by "Steve Lawrence (Jira)" <ji...@apache.org> on 2019/12/16 17:03:00 UTC

[jira] [Resolved] (DAFFODIL-2227) Develop a container for release candidates

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

Steve Lawrence resolved DAFFODIL-2227.
--------------------------------------
      Assignee: Steve Lawrence
    Resolution: Fixed

Fixed in commit e9526842a0165a6454df0050fff5ce6c4590fd91

> Develop a container for release candidates
> ------------------------------------------
>
>                 Key: DAFFODIL-2227
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2227
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Infrastructure
>            Reporter: Steve Lawrence
>            Assignee: Steve Lawrence
>            Priority: Major
>             Fix For: 2.5.0
>
>
> The [Release Workflow|https://cwiki.apache.org/confluence/display/DAFFODIL/Release+Workflow] is pretty throughly documented, but there are a lot of manual steps involved and it requires the release manager to have their environment set up properly, much of which could be automated.
> To improve reproducability and minimize the effects of a users environment, we should create a "release candidate container" that can be run via docker/podman/etc to perform all the neccesary steps to setup a clean environment to build and publish a release.



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