it is not a bad idea for adoption, but it would be nice to find out
if the rest of the community is OK with monitoring the chat room.
Can others respond here?
D.
--
--
Pavel Tupitsyn
GridGain Systems, Inc.
www.gridgain.com
Systems
www.gridgain.com
--
--
Pavel Tupitsyn
GridGain Systems, Inc.
www.gridgain.com
in public API public int getLength() with comment /**
Gets the length. */ is senseless , because it contains only obvious
information.
--ivan
On Thu, Jul 30, 2015 at 6:06 PM, Pavel Tupitsyn ptupit...@gridgain.com
wrote:
I agree.
Public things (classes/interfaces/methods/etc) should
process:
https://cwiki.apache.org/confluence/display/IGNITE/Sprint+Process
--AG
--
Regards,
Atri
*l'apprenant*
--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com
--
--
Pavel Tupitsyn
GridGain Systems, Inc
workflow.
Thanks,
On Tue, Jul 28, 2015 at 8:33 PM, Konstantin Boudnik c...@apache.org wrote:
On Tue, Jul 28, 2015 at 01:33PM, Pavel Tupitsyn wrote:
I hope so, it'd be horrible to do that on master!
Exactly!
But I do not see much sense in enforcing any kind of policy in personal
)
// rename = create new branch from the HEAD of old branch and delete
old
branch.
I think this schema will be more clear for contributors, commiters and
simple users.
Thoughts? Objections?
-- Artem --
--
--
Pavel Tupitsyn
GridGain Systems, Inc.
www.gridgain.com
://www.threadingbuildingblocks.org/) - it is open-source and pretty
light.
Does anyone has other ideas on this?
Vladimir.
--
--
Pavel Tupitsyn
GridGain Systems, Inc.
www.gridgain.com
to handle
both
scenarios in the same way. But which way is correct? Thoughts?
The messaging way sounds more logical to me.
Vladimir.
--
--
Pavel Tupitsyn
GridGain Systems, Inc.
www.gridgain.com
