The issue with java documentation is resolved after opening
https://issues.apache.org/jira/browse/INFRA-14117. Now java doc for 3.6.0
is available at
https://ci.apache.org/projects/apex-core/apex-core-javadoc-release-3.6/index.html
- Tushar.
On Mon, May 8, 2017 at 11:11 AM, Tushar Gosavi
wrote:
[
https://issues.apache.org/jira/browse/APEXMALHAR-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise resolved APEXMALHAR-2481.
--
Resolution: Fixed
Assignee: Thomas Weise
Fix Version/s: 3.8.0
> Hig
[
https://issues.apache.org/jira/browse/APEXCORE-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16001657#comment-16001657
]
Sanjay M Pujare commented on APEXCORE-711:
--
Recapping my earlier analysis about
Now available at:
https://ci.apache.org/projects/apex-core/apex-core-javadoc-release-3.6/index.html
Ram
I don't have a strong preference either way and am fine with either policy.
Immediate archival of older releases has the benefit that we can address it
in a straightforward way as part of the release process. Is there any
advantage of keeping the older releases in svn as deleting a release from
svn
[
https://issues.apache.org/jira/browse/APEXCORE-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16001104#comment-16001104
]
Sanjay M Pujare commented on APEXCORE-711:
--
[~vrozov] we are working with Yarn/
[
https://issues.apache.org/jira/browse/APEXMALHAR-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000875#comment-16000875
]
ASF GitHub Bot commented on APEXMALHAR-2481:
Github user asfgit closed th
Github user asfgit closed the pull request at:
https://github.com/apache/apex-malhar/pull/617
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Is there a practical reason to keep old *source* releases in svn
assuming that there is no active development on the old branches and
that sources for old releases are available in archive, github and maven?
Thank you,
Vlad
On 5/8/17 06:39, Thomas Weise wrote:
I think the goal of the archiva
I think the goal of the archival policy is to prevent unlimited growth of
releases in the dist folder, not to impose a narrow definition of "under
development". Looking at the releases available for other projects, I don't
think there is any issue considering the last two release branches "under
de
10 matches
Mail list logo
