On 22 June 2015 at 19:14, aconway <acon...@redhat.com> wrote: > On Tue, 2015-06-16 at 23:38 -0400, Rafael Schloming wrote: >> I'd like to get the proton-j-reactor branch into 0.10 also. It should >> be >> ready soon, so if py3k can be sorted and merged in a similar >> timeframe we >> could target a release for the end of the month. > > The C++ and Go bindings are also close to ready. I would not advocate > delaying the release just for them if there are already key features > that people are asking for, but if we can get them ready in time it > would be good to include them. >
If they are ready I would say include them. If they aren't, then I release without them and do another release once they are. I'd say the same for most large additions if they aren't needed to complete / round out other changes already made for the next release. I think we tend to be guilty of putting everything in together, resulting in a big release that can then drag on a bit, making it more difficult to respond quickly if the need arises, which in turn makes us want to complete the cycle by including yet more stuff into the release just to avoid it having to wait around for a while until the following release happens. Robbie >> >> --Rafael >> >> On Tue, Jun 16, 2015 at 3:32 PM, Flavio Percoco <fla...@redhat.com> >> wrote: >> >> > Greetings, >> > >> > I've been looking with great pleasure all the progress happening in >> > proton lately and I was wondering whether it'd be possible to have >> > an >> > 0.10 release cut soon. >> > >> > There are some bugfixes I'm personally interested in but also some >> > important changes (specifically in the python bindings) that will >> > make >> > consuming proton easier for users (OpenStack among those). >> > >> > Is there a chance for the above to happen any time soon? >> > >> > Can I push my request a bit further and ask for the py3k code to be >> > merged as well? >> > >> > All the above are key pieces to make proton more consumable and >> > allow >> > for services like OpenStack to fully adopt it. >> > >> > Thanks, >> > Flavio >> > >> > -- >> > @flaper87 >> > Flavio Percoco >> >
