Re: [api-dev] Optional Parameters in Starbasic function call

[Andrew Jensen]

My personal opinion here (again without having judged the concrete case) is that if an issue is annoying people for that long time, and this is shown by votes, constant complaints, whatever, it should get some points on the pro-include-in-2.0.x side - it might be considered a "customer escalation" then :). I would think that if the defect merited the allocation of the developrs time to implement the fix it merits the time to be tested to the extent needed for release. The fact will remain that only the development staff involved can judge what that effort really is. Look at it this way, was it really the best allocation of the developers time - a very tight resource, I hae no doubt, if the resoures to do what is necessary to get the fruits of their effort out to the users is not also made available? Final point, they are called maintanence releases because they incorporate fixes to known defects. Well, but that definition is to broad ... The number of known defects (just query IZ) is much higher than we will fixed for even "OOo Much Later". I didn't say that maintenance releases are such because they include fixes to all known defects, just that they by definition include fixes to defects. But - Speaking of useful allocation of time, - enough of this subject for me perhaps. Just slip on into Issuzilla and target it for 2.0.3..no one will notice that you did it... ;-) Drew