You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by Pallavi Rao <pa...@inmobi.com> on 2015/11/30 13:27:10 UTC
Apache Falcon 0.9 release scope and plan
All,
In keeping with our commitment to make frequent releases and also
considering the upcoming holiday season, I propose the following timeline
for the 0.9 release:
- Feature freeze (Any feature requiring dev. work beyond this date will
not be considered for v0.9) : 31st Dec 2015
- Code freeze (No bug fixes either unless it is a critical/blocker bug):
8th Jan 2016
- QA sign off : 14th Jan 2016
- First Release candidate : 15th Jan 2016
Although the timelines are tentative, lets try and work towards these dates.
Scope (apart from minor enhancements and features):
1. Native scheduler with time-based scheduling (If we can accommodate
QA, will consider Data availability based too).
2. Data import from database (via Scoop) as a lifecycle extension.
3. Support for Effective time of entity update to be in the past.
4. Instance Search capability.
5. Process SLA monitoring ??
Anything else we can accommodate within these timelines? I will start
moving currently resolved (after 0.8) and patch available JIRAs to 0.8
branch shortly
Let me know your thoughts/inputs on the dates and the scope.
Thanks and regards,
Pallavi
--
_____________________________________________________________
The information contained in this communication is intended solely for the
use of the individual or entity to whom it is addressed and others
authorized to receive it. It may contain confidential or legally privileged
information. If you are not the intended recipient you are hereby notified
that any disclosure, copying, distribution or taking any action in reliance
on the contents of this information is strictly prohibited and may be
unlawful. If you have received this communication in error, please notify
us immediately by responding to this email and then delete it from your
system. The firm is neither liable for the proper and complete transmission
of the information contained in this communication nor for any delay in its
receipt.
Re: Apache Falcon 0.9 release scope and plan
Posted by Peeyush Bishnoi <bp...@yahoo.co.in>.
For 0.9, I am planning to provide "Add CLI option to display captured replication metrics.
Thanks---Peeyush
On Monday, 30 November 2015 8:33 PM, Sandeep Samudrala <sa...@gmail.com> wrote:
safe mode in falcon can go as part of falcon 0.9
thanks,
-sandeep
On Nov 30, 2015 8:25 PM, "Pallavi Rao" <pa...@inmobi.com> wrote:
> All,
> In keeping with our commitment to make frequent releases and also
> considering the upcoming holiday season, I propose the following timeline
> for the 0.9 release:
>
> - Feature freeze (Any feature requiring dev. work beyond this date will
> not be considered for v0.9) : 31st Dec 2015
> - Code freeze (No bug fixes either unless it is a critical/blocker bug):
> 8th Jan 2016
> - QA sign off : 14th Jan 2016
> - First Release candidate : 15th Jan 2016
>
> Although the timelines are tentative, lets try and work towards these
> dates.
>
> Scope (apart from minor enhancements and features):
>
> 1. Native scheduler with time-based scheduling (If we can accommodate
> QA, will consider Data availability based too).
> 2. Data import from database (via Scoop) as a lifecycle extension.
> 3. Support for Effective time of entity update to be in the past.
> 4. Instance Search capability.
> 5. Process SLA monitoring ??
>
> Anything else we can accommodate within these timelines? I will start
> moving currently resolved (after 0.8) and patch available JIRAs to 0.8
> branch shortly
>
> Let me know your thoughts/inputs on the dates and the scope.
>
> Thanks and regards,
> Pallavi
>
> --
> _____________________________________________________________
> The information contained in this communication is intended solely for the
> use of the individual or entity to whom it is addressed and others
> authorized to receive it. It may contain confidential or legally privileged
> information. If you are not the intended recipient you are hereby notified
> that any disclosure, copying, distribution or taking any action in reliance
> on the contents of this information is strictly prohibited and may be
> unlawful. If you have received this communication in error, please notify
> us immediately by responding to this email and then delete it from your
> system. The firm is neither liable for the proper and complete transmission
> of the information contained in this communication nor for any delay in its
> receipt.
>
Re: Apache Falcon 0.9 release scope and plan
Posted by Sandeep Samudrala <sa...@gmail.com>.
safe mode in falcon can go as part of falcon 0.9
thanks,
-sandeep
On Nov 30, 2015 8:25 PM, "Pallavi Rao" <pa...@inmobi.com> wrote:
> All,
> In keeping with our commitment to make frequent releases and also
> considering the upcoming holiday season, I propose the following timeline
> for the 0.9 release:
>
> - Feature freeze (Any feature requiring dev. work beyond this date will
> not be considered for v0.9) : 31st Dec 2015
> - Code freeze (No bug fixes either unless it is a critical/blocker bug):
> 8th Jan 2016
> - QA sign off : 14th Jan 2016
> - First Release candidate : 15th Jan 2016
>
> Although the timelines are tentative, lets try and work towards these
> dates.
>
> Scope (apart from minor enhancements and features):
>
> 1. Native scheduler with time-based scheduling (If we can accommodate
> QA, will consider Data availability based too).
> 2. Data import from database (via Scoop) as a lifecycle extension.
> 3. Support for Effective time of entity update to be in the past.
> 4. Instance Search capability.
> 5. Process SLA monitoring ??
>
> Anything else we can accommodate within these timelines? I will start
> moving currently resolved (after 0.8) and patch available JIRAs to 0.8
> branch shortly
>
> Let me know your thoughts/inputs on the dates and the scope.
>
> Thanks and regards,
> Pallavi
>
> --
> _____________________________________________________________
> The information contained in this communication is intended solely for the
> use of the individual or entity to whom it is addressed and others
> authorized to receive it. It may contain confidential or legally privileged
> information. If you are not the intended recipient you are hereby notified
> that any disclosure, copying, distribution or taking any action in reliance
> on the contents of this information is strictly prohibited and may be
> unlawful. If you have received this communication in error, please notify
> us immediately by responding to this email and then delete it from your
> system. The firm is neither liable for the proper and complete transmission
> of the information contained in this communication nor for any delay in its
> receipt.
>