Hi Insectiside,
There are two concerns raised in your comments. One is regarding long pending features and second on time line for features which are in development status. I wish to provide an update on our model.
Generally we pick a set of features and start on them . There could be features which are requested long back and we have not yet started. We will list the features which we have started or about to start in road map section. There may be a few more features which we are working (and not included in the road map list), but road map will contain most of the list. We cannot provide update on feature out side the current set (as the next set of features cannot be finalized ahead of time).
Among the above list we have not yet started on (4), (5) and (6) and hence cannot provide time line for them.
Earlier we use to announce time schedule for features which are in progress. We found that our customers have committed feature schedule to their management based on our schedule. When we miss the schedule, we put undue pressure on our customers too (who have committed it internally). This is where we want to restrict our self on announcing time schedules till we have clarity (recent past). We are planning to update the time line for the feature in the road map page once we get visibility (so road map page will be single page to watch for schedules rather than multiple forum posts).
Yes I agree we have missed time line grossly for feature like new rich text area (or we could call this as an issue rather a feature) due to combining the new editor over doc type inclusion in client.
As far as new UI is concerned we know there is lot of work involved and hence we have not committed any time line (and wont do so till we complete some more back ground and design activity). Similarly introducing Purchase Request is a new feature (a preliminary entity before purchase order) and we know it will take time to implement the feature.
For issues, we are planning to fix them with in fixed time frame. This is one reason where we are seeing more issues fixes included in the recent service packs. Some of the issues are long pending. This will ensure better stability for the product. I agree there are breakages during issue fixes and we will focus more to avoid it.
To summarize :
1) Will include the on going features in road map section and publish time line against them once we get clarity
2) Our true apologies that we will not be providing time line for features which we have not yet started
3) Will look to fix issues with in fixed time frame and to avoid breakages due to new features / issue fixes.
regards,
Uma..
SDP team..
There are two concerns raised in your comments. One is regarding long pending features and second on time line for features which are in development status. I wish to provide an update on our model.
Generally we pick a set of features and start on them . There could be features which are requested long back and we have not yet started. We will list the features which we have started or about to start in road map section. There may be a few more features which we are working (and not included in the road map list), but road map will contain most of the list. We cannot provide update on feature out side the current set (as the next set of features cannot be finalized ahead of time).
Among the above list we have not yet started on (4), (5) and (6) and hence cannot provide time line for them.
Earlier we use to announce time schedule for features which are in progress. We found that our customers have committed feature schedule to their management based on our schedule. When we miss the schedule, we put undue pressure on our customers too (who have committed it internally). This is where we want to restrict our self on announcing time schedules till we have clarity (recent past). We are planning to update the time line for the feature in the road map page once we get visibility (so road map page will be single page to watch for schedules rather than multiple forum posts).
Yes I agree we have missed time line grossly for feature like new rich text area (or we could call this as an issue rather a feature) due to combining the new editor over doc type inclusion in client.
As far as new UI is concerned we know there is lot of work involved and hence we have not committed any time line (and wont do so till we complete some more back ground and design activity). Similarly introducing Purchase Request is a new feature (a preliminary entity before purchase order) and we know it will take time to implement the feature.
For issues, we are planning to fix them with in fixed time frame. This is one reason where we are seeing more issues fixes included in the recent service packs. Some of the issues are long pending. This will ensure better stability for the product. I agree there are breakages during issue fixes and we will focus more to avoid it.
To summarize :
1) Will include the on going features in road map section and publish time line against them once we get clarity
2) Our true apologies that we will not be providing time line for features which we have not yet started
3) Will look to fix issues with in fixed time frame and to avoid breakages due to new features / issue fixes.
regards,
Uma..
SDP team..