Hi Vineet, Thank you for your comment, I will add timeline on release page as part of the plan.
Basically, I expect by 30th Oct., we can have tar balls available for downloading, and before that I reserve about 1.5 month for voting progress according to previous experiences. So basically, I think we can cut branch for new release at mid Sept. So that means we have no more than 2 months for fixing and new feature delivery. As delivering pluggable external storage requires some time. If necessary, I think it is ok to move target date 2 weeks earlier. Does this rough time schedule make sense? What's your opinion? I will add Umbrella JIRAS on that page as well. Best, Yi Jin (yjin) On Thu, Jul 20, 2017 at 3:52 PM, Vineet Goel <vvin...@apache.org> wrote: > Hi Yi, > > Thank you for the initiative. I have some feedback that we can discuss here > and collect further input on. > > a) Putting a timeline on releases (such as October 31st here) may have some > downsides to the process. My thoughts are that more frequent releases give > users access to features and fixes faster, from a stable branch. Release > momentum is good to have in any project. For instance, master branch is > already 75+ commits ahead of 2.2.0.0-incubating, since that branch was cut > a a couple of months back. > > b) Also, it may help to add Umbrella JIRAs on that page, associated to the > new features. If certain features are too large to finish in a given > release, they can always ride the next release vehicle. > > It would be good to hear thoughts from others. > > Thanks! > Vineet > > > > > On Wed, Jul 19, 2017 at 6:15 PM Yi JIN <y...@apache.org> wrote: > > > Hi Apache HAWQ community, > > > > Thank you guys for your trust, I drafted one release plan for next > version > > 2.3.0.0 that has been update in wiki as below. Please feel free to > comment > > and any input is welcome. Thank you again. > > > > > > https://cwiki.apache.org/confluence/display/HAWQ/Apache+HAWQ+2.3.0.0- > incubating+Release > > > > > > Best, > > Yi Jin (yjin) > > >
