[Vtigercrm-developers] Roadmap 6.5 and 7

Tue Apr 19 11:50:29 GMT 2016

Could’t agree more!

A few things:

- I see people interested in contribute, improve code, find errors etc like @preexo in http://code.vtiger.com/vtiger/vtigercrm/merge_requests/25
and @lord_alan in many places but this will never work because the way vtiger team is proceeding, very slow.

- I believe @preexo have more merge requests and at least give him a response as he said:
“
@prasad <http://code.vtiger.com/u/prasad> fair enough to defer this pull request for now. Until what time are you planning to defer it to?

There are many more changes to be made, so far it's only scratching the surface. The ultimate goal should be no more notices/warnings/stricts and everything working with PHP7. Many more dependencies (3rd party libraries) could also be updated, it's almost an entire task for itself.

Depending on this pull request I would like to pick this work again, but would defer the maintenance work for now until you found time to review this pull request. Thanks, looking forward for feedback.

“
But this was 2 months ago

- And most important they don’t lead community!

- Imagine this scenario: 
You are sending merge requests but they announced vtiger 7 and by the time when released code is changed in a way that your work doesn’t make sense.

This is just one way cooperation. I never heard vtiger team suggesting something like: Hey community friends, lets focus in errors or php 7 compatibility, or lets update libraries dependences, propose your merge requests or similar. This way we will include progressive in new version!

With this kind of roadmap community does’t have information about what is going on. 
This is more like, “just wait because we will release a new version”.

> 3. Roadmap - We'll release 6.5 by end of Q1, and Vtiger 7.0 in Q3. 

Sorry about this fragmented information but you all that keep your eyes in forum, code.vtiger.com know all this and thats why i’m not posting full detailed information or cases.
And when vtiger team say 6.5 will be released, sorry to say but this is “just” a pack os some merge requests that you didn’t pronunciate in most of them.

Best Regards.

Manuel

> No dia 07/04/2016, às 12:50, Tim Mohrbach <preexo at googlemail.com> escreveu:
> 
> This statement makes sense if there will actually be more workforce going into the open source project in future with more people working on it employed with the vtiger company. 
> That would be great, since it has felt even less actively being developed lately. 
> Not complaining, just saying. 
> 
> We have internally started to call vtiger the abandoned child a while ago already. I would be so happy to be shown the opposite by you. 
> 
> Best regards 
> 
> 
> On April 7, 2016 6:17:17 PM GMT+08:00, Prasad <prasad at vtiger.com> wrote:
> Busy onboarding new members to team, likely to slip the guesstimated release time.
>  
> 
> --
> FB <http://www.facebook.com/vtiger> I Twit <http://twitter.com/vtigercrm> I LIn <https://www.linkedin.com/company/1270573?trk=tyah> I Blog <https://blogs.vtiger.com/> I Website <https://www.vtiger.com/>
> On Thu, Apr 7, 2016 at 3:14 PM, Conrado Maggi <comaggi at gmail.com <mailto:comaggi at gmail.com>> wrote:
> Hi,
> 
> Is this -> We'll release 6.5 by end of Q1, and Vtiger 7.0 in Q3.  still valid?
> 
> Cheers,
> Conrado
> 
> On Thu, Jan 7, 2016 at 6:39 PM, Sreenivas Kanumuru <svk at vtiger.com <mailto:svk at vtiger.com>> wrote:
> Happy New year!
> 
> We are excited about the developments coming to Vtiger open source edi! tion. While it will not have all the features of our cloud edition, it will continue to draw many of the enhancements that we roll out to the cloud edition.
> 
> These are the priorities for us in 2016.
> 
> 1. To facilitate community contributions and collaboration, we recently moved to git (code.vtiger.com <http://code.vtiger.com/>). We will be reviewing the contributions and respond promptly. 
> 2. Promote extensions development and strengthen marketplace. While Open source doesn't have all cloud edition features, through marketplace customers have access to a rich set of functionality. 
> 3. Roadmap - We'll release 6.5 by end of Q1, and Vtiger 7.0 in Q3. 
> 
> As to the question of making Vtiger On Demand code open source, the answer is that we do not foresee doing that. On Demand service is a collection of applications that are running on different ser! vers, CRM being one of them. There is Global search that is driven through Solr. Then there is Email campaigns service that we run through a network of servers. And there is a Email Archival and Response service for converting emails into tickets, ..etc. In addition, Notifications, and some of the connectors such as Quickbooks, and Zapier require intermediate services.
> 
> Regards,
> Sreenivas 
> 
> 
> 
> thank you,
> Sreenivas
> 
> On Thu, Jan 7, 2016 at 8:40 PM, Stacey Johnson <stacey.johnson110 at gmail.com <mailto:stacey.johnson110 at gmail.com>> wrote:
> :o)
> 
> On Thu, Jan 7, 2016 at 10:06 PM, John Crisp <john at reetspetit.net <mailto:john at reetspetit.net>> wrote:
> On 07/01/16 15:53, Stacey Johnson wrote:
> > @Preexo @Alan ===> no way they will do so. Wanna bet?
> >
> 
> Lord you like taking easy money.... that's like robbing a blind man :-)
> 
> 
> 
> _______________________________________________
> http://www.vtiger.com/ <http://www.vtiger.com/>
> 
> 
> _______________________________________________
> http://www.vtiger.com/ <http://www.vtiger.com/>
> 
> 
> _______________________________________________
> http://www.vtiger.com/ <http://www.vtiger.com/>
> 
> 
> _______________________________________________
> http://www.vtiger.com/ <http://www.vtiger.com/>
> 
> 
> 
> http://www.vtiger.com/ <http://www.vtiger.com/>
> -- 
> Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
> _______________________________________________
> http://www.vtiger.com/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20160419/79e74e18/attachment-0001.html>