It's traditional. We wait for the last minute to get our talk proposals
in for conferences.
Well, the last minute has arrived. The CFP for ApacheCon Seville closes
on September 9th, which is less than 2 weeks away. It's time to get your
talks in, so that we can make this the best ApacheCon yet.
Agreed. This improvement can further make the release process smoother. Should
definitely help in maintaining release cadence.
RegardsSrikanth Sundarrajan
> From: sandys...@gmail.com
> Date: Tue, 30 Aug 2016 14:19:44 +0530
> Subject: Re: Democratizing Release Notes
> To: dev@falcon.apache.org
>
+1. Agree with Pallavi and Ajay. Only important updates should be go into
release notes so that the list is not huge and easily readable.
On Tue, Aug 30, 2016 at 2:16 PM, Pallavi Rao wrote:
> This is nice!
>
> Don't think we can mandate that field as not all JIRAs will
[
https://issues.apache.org/jira/browse/FALCON-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15448467#comment-15448467
]
ASF GitHub Bot commented on FALCON-2133:
GitHub user muraliramasami opened a pull request:
GitHub user muraliramasami opened a pull request:
https://github.com/apache/falcon/pull/277
FALCON-2133: Disable the LogMover from FeedReplication on secure mode.
LogMover is only supported in case of un-secure mode. It has to be disable
in the secure mode. In FeedReplication test
This is nice!
Don't think we can mandate that field as not all JIRAs will need an entry
in Release Notes. Examples are falcon regression test suite updates, UT
changes, documentation updates, bugs reported that turn out to be usage
issues.
On Tue, Aug 30, 2016 at 2:09 PM, Srikanth Sundarrajan
+1. Would it help if we made the release notes field mandatory for marking the
jira closed ?
RegardsSrikanth Sundarrajan
> From: ajayyad...@apache.org
> Date: Tue, 30 Aug 2016 08:35:50 +
> Subject: Democratizing Release Notes
> To: dev@falcon.apache.org
>
> Hello everyone,
>
> Continuing
Hello everyone,
Continuing on our effort to automating change log and release notes, I am
happy to share with you that we now have the ability to automatically
generate release notes through Apache Yetus.
*How does it work?*
We have introduced a new field in JIRA - Release Notes. Every
Murali Ramasami created FALCON-2133:
---
Summary: Disable the LogMover assertions from FeedReplication on
Secure Mode
Key: FALCON-2133
URL: https://issues.apache.org/jira/browse/FALCON-2133
Project:
[
https://issues.apache.org/jira/browse/FALCON-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15448221#comment-15448221
]
Ajay Yadava commented on FALCON-1440:
-
I wanted to ensure backward compatibility so I was waiting for
[
https://issues.apache.org/jira/browse/FALCON-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ajay Yadava updated FALCON-1440:
Issue Type: Sub-task (was: Bug)
Parent: FALCON-1871
> Better json for triage api
>
[
https://issues.apache.org/jira/browse/FALCON-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ajay Yadava updated FALCON-475:
---
Issue Type: Sub-task (was: Improvement)
Parent: FALCON-1871
> Add Version to the REST APIs
>
[
https://issues.apache.org/jira/browse/FALCON-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ajay Yadava reassigned FALCON-475:
--
Assignee: Ajay Yadava
> Add Version to the REST APIs
>
>
>
Murali Ramasami created FALCON-2131:
---
Summary: Add Hive Replication server side extension Test cases
Key: FALCON-2131
URL: https://issues.apache.org/jira/browse/FALCON-2131
Project: Falcon
Murali Ramasami created FALCON-2132:
---
Summary: Add HDFS Snapshot Replication server side extension Test
cases
Key: FALCON-2132
URL: https://issues.apache.org/jira/browse/FALCON-2132
Project:
Murali Ramasami created FALCON-2129:
---
Summary: Add test cases for server side extensions in Falcon
Key: FALCON-2129
URL: https://issues.apache.org/jira/browse/FALCON-2129
Project: Falcon
16 matches
Mail list logo