[Vtigercrm-developers] Roadmap 6.5 and 7

[Luca saba]

Hi all. I'm absolutely a newbie in vtiger. I've really appreciated its
lean learning curve (at least from the client's perspective). What
stops me a little bit, by beeing more active, is the lack of
information about vtiger's goals.
It's great to develop new features and to correct bugs. But how is it
possibile to put a great effort not knowing if your code is going to
be v7 compliant ?

One of the greates hurdles I've found trying to write new featues is
that vtiger's code is not always decoupled. And that force you to
touch the core. And maintaining code that need a core's modification
can be a hell expecially if you don't now how the core is going to
evolve in the new version.

As far as I could search I didn't find anything about what's going to
be in the new version and I don't think we are moving to a new major
version just because there's a new UI. An opensource project should
share with all developers what's going to happen.

L.

2016-04-29 10:50 GMT+02:00 Alan Bell <alan.bell at libertus.co.uk>:
> On 29/04/16 07:02, Preexo wrote:
>>
>> Alan Bell-6 wrote
>>>
>>> >but I got a heap of merges accepted on
>>> >code.vtiger.com over the past few days, so I am not too distressed at
>>> >the moment.
>>
>> I just saw that on code.vtiger.com and it made my day! I will commit a few
>> more things in the next few weeks as well and hope for the best,
>
> worth noting for the vtiger folk that the best way to motivate people to
> contribute more stuff is to review issues and action merges in a reasonable
> timescale, (accepting or rejecting is fine, leaving it is not so good) if I
> have 10 outstanding merge requests sitting there with no feedback I am not
> going to do much more, but if they get merged then I am going to try and
> fill up the queue again, and if they get rejected I am going to fix them and
> try again.
>
> Sometimes what is needed on an issue is a little discussion about the right
> way to fix it before someone can go ahead and do the work and propose a
> merge - especially for situations like this one:
> http://code.vtiger.com/vtiger/vtigercrm/issues/184 where I want a feature I
> know is in the on-demand and I can implement in the open source, but that is
> a bit of a redundant effort (actually I already did it for a customer so not
> too much extra effort) and I think it just makes merging harder in the
> future.
>
> Alan.
> _______________________________________________
> http://www.vtiger.com/



-- 
It is easier to move a problem around (for example, by moving the
problem to a different part of the overall network architecture) than
it is to solve it.
6th truth - rfc1925
------------------------------------------------------------------
Einstein: Imagination is more important than knowledge. For knowledge
is limited, whereas imagination embraces the entire world, stimulating
progress, giving birth to evolution.
------------------------------------------------------------------
Heinlein: Specialization is for Insects