You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Christian Amend (JIRA)" <ji...@apache.org> on 2014/02/04 12:28:08 UTC
[jira] [Updated] (OLINGO-144) After release improvements
[ https://issues.apache.org/jira/browse/OLINGO-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Amend updated OLINGO-144:
-----------------------------------
Description:
After the release is build we should work in the feedback which was put on hold to build the release. This includes:
- Delete blank line in NOTICE file
- Check SHA checksumgeneration and naming e.g. sha1 or sha512
- Check Disclaimer content as it is not exaclty like on http://incubator.apache.org/guides/branding.html#disclaimers and thus should have been approved by the IPMC board.
- Check if pure source distributions should contain a notice that 3rd party libraries are used if it is build
- Update release documentation
- Update verification site on how to use sha512 and md5
was:
After the release is build we should work in the feedback which was put on hold to build the release. This includes:
- Delete blank line in NOTICE file
- Check SHA checksumgeneration and naming e.g. sha1 or sha512
- Check Disclaimer content as it is not exaclty like on http://incubator.apache.org/guides/branding.html#disclaimers and thus should have been approved by the IPMC board.
- Check if pure source distributions should contain a notice that 3rd party libraries are used if it is build
- Update release documentation
> After release improvements
> --------------------------
>
> Key: OLINGO-144
> URL: https://issues.apache.org/jira/browse/OLINGO-144
> Project: Olingo
> Issue Type: Improvement
> Components: odata2-core
> Affects Versions: V2 1.1.0
> Reporter: Christian Amend
> Assignee: Christian Amend
> Fix For: V2 1.2.0
>
>
> After the release is build we should work in the feedback which was put on hold to build the release. This includes:
> - Delete blank line in NOTICE file
> - Check SHA checksumgeneration and naming e.g. sha1 or sha512
> - Check Disclaimer content as it is not exaclty like on http://incubator.apache.org/guides/branding.html#disclaimers and thus should have been approved by the IPMC board.
> - Check if pure source distributions should contain a notice that 3rd party libraries are used if it is build
> - Update release documentation
> - Update verification site on how to use sha512 and md5
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)