Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
MapReduce >> mail # dev >> Next releases

Copy link to this message
Re: Next releases

On Nov 13, 2013, at 1:55 PM, Jason Lowe <[EMAIL PROTECTED]> wrote:
> +1 to limiting checkins of patch releases to Blockers/Criticals.  If necessary committers check into trunk/branch-2 only and defer to the patch release manager for the patch release merge.  Then there should be fewer surprises for everyone what ended up in a patch release and less likely the patch release becomes destabilized from the sheer amount of code churn.  Maybe this won't be necessary if everyone understands that the patch release isn't the only way to get a change out in timely manner.

I've updated https://wiki.apache.org/hadoop/Roadmap to reflect that we only put in Blocker/Critical bugs into Point Releases.

Committers, from now, please exercise extreme caution when committing to a point release: they should only be limited to Blocker bugs.

NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.