I agree with Kostas, and believe that postponing will imo straight up
not work since people tend to be *very* busy close to a release, even
without having to port features to several APIs.
I furthermore don't think we will get anywhere by creating one policy to
rule them all (especially a rigi
+1
Looks nice!
On 27 Sep 2014, at 21:04, Kostas Tzoumas
mailto:ktzou...@apache.org>> wrote:
Wow so cool!
On Sat, Sep 27, 2014 at 2:52 PM, Stephan Ewen
mailto:se...@apache.org>> wrote:
Wow, amazing :-) And so quickly done!
Am 27.09.2014 11:14 schrieb "Ufuk Celebi"
mailto:u...@apache.org>>:
Wow so cool!
On Sat, Sep 27, 2014 at 2:52 PM, Stephan Ewen wrote:
> Wow, amazing :-) And so quickly done!
> Am 27.09.2014 11:14 schrieb "Ufuk Celebi" :
>
> >
> > On 27 Sep 2014, at 08:00, Márton Balassi wrote:
> >
> > >> I hope I could get you excited too :)
> >
> > +1 :-)
>
If we allow out-of-sync APIs (and backends) until the time of a release,
aren't we just postponing the syncing problem to the time of the release,
which is a pretty bad time to have such a problem?
On Fri, Sep 26, 2014 at 8:49 PM, Robert Metzger wrote:
> Hi,
>
> I'm also in favor of having a st
Wow, amazing :-) And so quickly done!
Am 27.09.2014 11:14 schrieb "Ufuk Celebi" :
>
> On 27 Sep 2014, at 08:00, Márton Balassi wrote:
>
> >> I hope I could get you excited too :)
>
> +1 :-)
On 27 Sep 2014, at 08:00, Márton Balassi wrote:
>> I hope I could get you excited too :)
+1 :-)
