+1 For making Micro Releases pure bug fix releases.
We should keep in mind though that each Minor release will then mean we
have to support one more branch.
So we should make sure we support only a certain number of branches at
the same time and support each branch for a minimum time like e.g. one
year. If these numbers were not already decided we should discuss and
decide them in a separate thread.
Christian
Am 25.06.2012 09:14, schrieb Guillaume Nodet:
Same feeling here, though I think we should learn from that and be
more vigilant about not introducing new features or behavioral changes
in micro releases, that should have been done in 2.3.
+1
On Sun, Jun 24, 2012 at 3:14 PM, Ioannis Canellos <ioca...@gmail.com> wrote:
Ideally, a micro release should guarantee forward and backward
compatibility.
I'd say though that the particular issue doesn't sound like a show stopper
to me.
--
*Ioannis Canellos*
*
FuseSource <http://fusesource.com>
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
