+1 for thinking about minor release. Frequent releases are usually good for any software. With first release done and all license issues resolved, the upcoming releases should be smooth.
For incubating project you have overhead of a week for voting (both dev and incubator list), but would become only dev when the project becomes TLP. Thanks Amareshwari On Thu, Apr 14, 2016 at 6:16 AM, Hao Chen <[email protected]> wrote: > Yes , too frequency is not very good, but just for this early stage, rapid > iteration by releasing some minor versions will help for stabilizing the > main features ASAP. > > Thanks, > Hao > > > On Apr 14, 2016, at 12:12 AM, Zhang, Edward (GDI Hadoop) < > [email protected]> wrote: > > > > +1, I think we need 0.3.1, what we need care about is the overhead for > frequent release. > > > > Thanks > > Edward > > > > From: Hao Chen <[email protected]> > > Reply-To: "[email protected]" < > [email protected]> > > Date: Wednesday, April 13, 2016 at 6:00 > > To: "[email protected]" < > [email protected]> > > Subject: [Discussion] Release v0.3.1 including related bug fix and > documentation based on v0.3.0 > > > > How do you think release a stabilized version v0.3.1 including related > critical bug fix and well-documentation (WIP) in next few weeks, based on > v0.3.0 (released 20 days ago)? > > > > - Hao >
