[
https://issues.apache.org/jira/browse/UIMA-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6335:
---------------------------------------------
Description:
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)
- (x) [RUTA] Integrate building of Eclipse update sites into the build
- (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
was:
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.
- (/) Drop the binary release package of uimaFIT - the source release and
obtaining the artifacts via Maven Central should be sufficient (UIMA-6448)
----
- Drop (most) binary ZIP releases and only offer source, Maven and for the Java
SDK / Ruta the Eclipse update site:
-- Rationale: The binary ZIPs use separate LICENSE/NOTICE files which need to
be checked/maintained - and this cannot be easily done automatically
> 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)
> - (x) [RUTA] Integrate building of Eclipse update sites into the build
> - (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.7#820007)
