[Vtigercrm-developers] Roadmap 6.5 and 7

[Manuel Fernando]

> PHP 7 - effort on it to start after 6.5.0 - please file it on code.vtiger.com <http://code.vtiger.com/>That is the intention. I wasn’t sarcastic.

But without your cooperation, it’s almost impossible because no response for some start work like @preexo did.
So do you expect people start send commits hover others work?
We will be looking for same fixes, improvements and that’s a waste of time.

If yes, thats a nonsense because everything is stuck and with no reviews.

I want to help, but only together it´s possible.

Best Regards.

Manuel

> No dia 02/05/2016, às 06:31, Prasad <prasad at vtiger.com> escreveu:
> 
> PHP 7 - effort on it to start after 6.5.0 - please file it on code.vtiger.com <http://code.vtiger.com/>
> 
> --
> 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 Sun, May 1, 2016 at 11:38 PM, Matteo Baranzoni <info at greenbitweb.com <mailto:info at greenbitweb.com>> wrote:
> @prasad
> What about php7 compatibility?
> 
> Il 29/apr/2016 16:45, "Prasad" <prasad at vtiger.com <mailto:prasad at vtiger.com>> ha scritto:
> I have summarized the targets that is on the table:
> 
> 6.5 Release Goal (Q2 / early Q3 2016)
> More focused on bug-fixes, merge-requests and minor features.
> Features that demands less core-framework changes will be pulled from Ondemand.
> 7.0 Release Goal (ETA - tentative 2017)
> Vtiger 7 Layout
> Enabling Multi-layout support need more community evaluation and feedback.
> Approved Ondemand features + core framework changes that are compatible to Opensource.
> What features will be in 7.0?
> To be discussed post 6.5.0 release.
> You are welcome to file requests on code.vtiger.com <http://code.vtiger.com/>.
> Would there be 6.6 instead of 7.0?
> Possible.
> Regards,
> Prasad
> Vtiger Team
> 
> --
> 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 Fri, Apr 29, 2016 at 4:07 PM, Manuel Fernando <ptdesigner at gmail.com <mailto:ptdesigner at gmail.com>> wrote:
> About create a new fork, speaking for myself, is not necessary because the fork is here.
> 
> And even if someone (individual or group) create a new fork some problems still there because the main problem now is not defined what must be done. New features, just fixes or improvements etc etc.
> A new fork, depending of witch people would drive that fork will always have a more specific way of thinking for their business cases or their knowledge areas.
> 
> We have now more tools than ever to contribute.
> For that, we should open a discussion like a webform for community put their needs and vote for improvements or new functionalities so we have a better understanding of what people is looking for.
> Vtiger team may have some data collected in the past years when vtiger is installed (selecting the business case).
> Community can have some similar if some "vote data" is collected.
> 
> Maybe we don’t need Vtiger 7 “depending of what is bringing for community”
> 
> About new features, sometimes they try to fill CRM’s in a way that gets massive and software looses his direction when try to include everything and that’s why extensions are great.
> 
> Best Regards.
> 
> Manuel
> 
> > No dia 29/04/2016, às 09:50, Alan Bell <alan.bell at libertus.co.uk <mailto:alan.bell at libertus.co.uk>> escreveu:
> >
> > On 29/04/16 07:02, Preexo wrote:
> >> Alan Bell-6 wrote
> >>> >but I got a heap of merges accepted on
> >>> >code.vtiger.com <http://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 <http://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 <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/ <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/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20160505/f64d211a/attachment.html>