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

Richard Eckart de Castilho resolved UIMA-6335.
----------------------------------------------
    Resolution: Done

Most points have been addressed. If the remaining open points remain pain 
points, open new issues for them on the GitHub issue tracker.

> Optimize release process
> ------------------------
>
>                 Key: UIMA-6335
>                 URL: https://issues.apache.org/jira/browse/UIMA-6335
>             Project: UIMA
>          Issue Type: Improvement
>            Reporter: Richard Eckart de Castilho
>            Assignee: Richard Eckart de Castilho
>            Priority: Major
>
> The release checklist is pretty long. To facilitate releases, we should see 
> what can be optimized / cut.
> - (/) {{README.md}} becomes version-independent and contains a proper project 
> description suitable as a GitHub repo landing page
> - (/) {{RELEASE_NOTES.md}} contains only version-specific release notes and 
> can be largely copy/pasted to the release announcments mail/website/etc.
> - (/) [uimaFIT] Drop the binary release package of uimaFIT - the source 
> release and obtaining the artifacts via Maven Central should be sufficient 
> (UIMA-6448)
> - (/) [UIMAJ] Integrate building of Eclipse update sites into the build 
> (UIMA-6443)
> - (/) [RUTA] Integrate building of Eclipse update sites into the build (part 
> of UIMA-6447)
> - (/) [UIMAJ] Use RC-auto-staging from Parent POM 15
> - (/) [uimaFIT] Use RC-auto-staging from Parent POM 15
> - (/) [RUTA] Use RC-auto-staging from Parent POM 15
> - (x) [UIMAJ] Put the examples in the UIMA Java SDK into a form where they 
> are convenient to use form the source distribution or find some other way of 
> providing them which does not require binary release package. In particular, 
> they should not be Eclipse projects but rather regular Maven projects
> - (x) [UIMAJ] Drop the binary release package of UIMA Java SDK - the source 
> release and obtaining the artifacts via Maven Central should be sufficient - 
> will safe us from having to maintain the LICENSE/NOTICE files for binary 
> releases



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to