falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pallavi Rao <pallavi....@inmobi.com>
Subject Apache Falcon 0.9 release - Code Freeze
Date Fri, 29 Jan 2016 12:16:48 GMT
Folks,
Calling for a code freeze on 0.9 branch as QA is running the final round of
regression. Any further issues fixed, unless critical, should go only into
trunk.

Thanks,
Pallavi

PS: FALCON-1782 will be exception as it already has its foot in the door
and has limited impact.


On Thu, Dec 31, 2015 at 2:50 PM, Pallavi Rao <pallavi.rao@inmobi.com> wrote:

> Hi,
> I have cut the 0.9 branch.
>
> Committers,
> Please ensure you commit any new patches to both 0.9 and trunk, if the
> patch needs to be in 0.9 release.
>
> Thanks,
> Pallavi
>
>
> On Wed, Dec 30, 2015 at 1:12 PM, Pallavi Rao <pallavi.rao@inmobi.com>
> wrote:
>
>> Scope for Falcon 0.9 release as it stands today:
>> 1. Native scheduler with time-based scheduling (Data availability is
>> still a stretch. Will release as alpha if dev-testing can be completed in
>> the next week).
>> 2. Data import/export.
>> 3. CLI option to display captured replication metrics (FALCON-1643
>> <https://issues.apache.org/jira/browse/FALCON-1643> is in
>> patch_available. Will not wait for this to cut the branch, but, will merge
>> to both trunk and 0.9 later).
>>
>> Let me know if there are any scope creeps or concerns.
>>
>> Thanks,
>> Pallavi
>> P. S : Some items from the original list have been removed as they could
>> not be completed in time for the release.
>>
>>
>> On Wed, Dec 2, 2015 at 9:11 PM, Peeyush Bishnoi <bpeeyush@yahoo.co.in>
>> wrote:
>>
>>> 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 <
>>> sandysmdl@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" <pallavi.rao@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.
>>> >
>>>
>>>
>>>
>>>
>>
>>
>

-- 
_____________________________________________________________
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.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message