I has been a long long time since the community meeting and I guess it is time to actually punch in all the suggestions and feature requests that lured on hastly scribbled notes into the more formal JIRA system.
Remember: if you feel particularly strong about one of those issues, vote for it. If you feel extra ordinarily strong about it and have a support contract, nag your support contact at Pentaho to add your case number to the JIRA-case. This ensures that the triage meeting gives that case a higher priority.
This list is probably not even complete. So if you encounter something new or see something that does not feel right, remember to file a JIRA case for it.
This is truly brilliant stuff. I’ve never before seen a software vendor harvesting bugs from genuine end users at a conference – yet of course it’s the perfect place to do it. Excellent!
In general software vendors dont want to hear your bugs in any case. Before you hand over the money you are important for them, after that you are just a cost factor. And bad support and not fixing the big, fat bugs – you hear those stories all the time. I dont want to be part of such an industry.
Personally I hate to leave things unfixed or to produce “checkbox items”. I see the customer’s role slightly different: After our users paid (with money and/or time) to use our software, they have good reasons to safeguard and maximize their investment returns by providing us accurate and useful information. Not the random (and usually exaggerated) stuff you hear before the sale – no, real world problems from real world users with real world businesses. Who else than actual users can tell us where we shall go and where we have strength and weaknesses.