Activity Update - Nov, 2009

Its been quite sometime on activity update, today I decided to complete this post even though the clock ticked 1:00′AM :)

Response on vtiger CRM 5.1.0 has been very exciting, with an approximately 70000+ product and 17000+ plug-ins downloads so far and Review & Rate @sourceforge.net has increased to 140!

We are thankful to community who are actively spreading the word and getting involved in community activities. Keep up the spirit and collaboration.

Our feedback monitoring team are happy to see the number of un-installation getting down significantly. They have been doing the follow-ups on these emails to help users to get started by orienting towards documentation links at http://wiki.vtiger.com or threads at http://forums.vtiger.com!

Our support team are focusing their energy reading through discussions on forums, blogs, feedback emails and co-ordinating with development team. They have been providing round-the-clock support to our users (who are using vtiger 4.x) and helping them to get migrated.

The challenge for optimization team has been raised since the last the last work that was rolled into 5.1.0

Our development team freezed the first phase of feature implementations for 5.2.0 and waiting for the integration completion. Bug-fixing phase is scheduled to start soon.

Will get back with few more updates, till then keep us posted with your usage or introducing it to your friends/clients.

Regards,
vtiger Team

9 Responses to “Activity Update - Nov, 2009”

  1. on 09 Nov 2009 at 1:56 pm hotel supplies

    Is also started work for implementation of OTP password to login in secure way: http://www.swekey.com/
    When I’ll know news I’ll write more about it.

  2. on 09 Nov 2009 at 2:16 pm David v.

    Hi Prasad,

    Thank you for this activity update.

    We really like working with 5.1 and the new webservices and vtlib features are so usefull when adapting the crm to customer’s needs. Thanks again to all the team !

    Could you point us to some documentation about the features in 5.2.0 ?

    David V.

  3. on 09 Nov 2009 at 9:17 pm Prasad

    @David,

    Did not get a chance to compile the new features or framework support on 5.2.0, will do as soon as I get time.

  4. on 10 Nov 2009 at 12:48 am Deep

    Dear Prasad,

    Good to see your update :)

    But I still miss the community process in deciding about the priority of features and the roadmap for vtiger. Should this not be a better idea if you compile the list of probable features for upcoming release long before development started and get some feedback or even voting, so that you guys develop only those things which are most needed by users.

    I’m sorry to say I’m seeing this is a repeat as in last many releases, we’ll get surprises [new features] will each development build and at the end [of 1 year] will have another release, with features missing that are requested even 3-4 years back.

    I’m no way trying to rant, but its my humble request to make some changes in your development and release process, its an Open Source environment.

    Release Early Release Often [Its been 4 months, we could have at least a bug fix update by now].

    Involve community in deciding about the direction of the development.

    Thanx & Regards,
    Deep

  5. on 10 Nov 2009 at 3:15 am steven

    Thanks for the update always good to get feedback from the dev team, keep up the amazing work!

    I would like to 2nd the recommendation to allow the community to vote on updates/bug fixes.

    I would also expect to see a maintenance/bug fix release by now v5.1.1 or something?

    any idea on a timeline for v5.2? Are we looking at this year still?

    keep up the good work!!
    Steve

  6. on 10 Nov 2009 at 3:52 am Prasad

    @Deep, @Steven

    Involve community in deciding about the direction of the development.

    We have always the open door for community to push in the ideas, contribute for development effort either by implementing the features or collaborate on the mailing list or forums etc… Many do contribute code, which our development team takes it forward and integrate.

    I would like to 2nd the recommendation to allow the community to vote on updates/bug fixes.

    This is a good idea, we respect it. We also aware of the fact, that it can turn-few members down if not taken in the right spirit. Personally, I have tried voting for issues on third-party libraries but the surprisingly its been ignored (due to the fact the vote is low!) and we finally ended up fixing it ourselves :)

    We target the bug fix by Priority and Impact of solution. Hence we demand more clarification when the issue is reported on trac or being discussed on forums. The community can help in providing test-script or steps to reproduce the issue or even sharing patches for the same.

    Release Early Release Often [Its been 4 months, we could have at least a bug fix update by now].

    Will take us sometime to get into this practice, we are learning.

  7. on 10 Nov 2009 at 4:02 am Deep

    Prasad,

    One thing I really love about you is to accept even the strongest critisism in very positive and open way, but sadly things just stop there :)

    I hope we see some change this time around :)

    To start with, will really appreciate if you can give some rough roadmap. It can come with one big disclaimer that it can change if circumstances require, but at least this will give some input to lot of your partners who need this info for their planning.

    Things which are upcoming
    Probable date of fix/patch [if any]
    Probable date of next release [5.2]

    And don’t worry, you are doing great, its just sometimes… ;)

  8. on 15 Dec 2009 at 3:57 am steve

    Hi Guys

    Any more news on the dev of 5.2?

    looking forward to some updates

    steve

  9. on 15 Dec 2009 at 6:21 pm Bernard

    Hi Prasad,

    Thank you so much for all the teamwork that has gone into 5.1. It is a huge leap over 5.04 and I imagine 5.2 will provide even more functionality.

    That said, I have to vote with Deep on the Roadmap.

    Surely votes on the roadmap direction can be strengthened/reduced according to the assigned membership rating of those who vote.

    I am a firm advocate of those who add value to the project should get at least a look into where the direction is going. Those who just drop in for a month, do a big rant about what’s missing and then leave for good, certainly have no place in leading the development roadmap.

    Those who have senior/contributor or higher status should be allowed some say in the process.

    BTW I’m looking for a Tabbed interface in each module.

    Keep up the excellent work Prasad.

    Cheers
    Bernard

Trackback URI | Comments RSS

Leave a Reply

Enter your e-mail address to receive notifications when there are new posts: