- This topic has 2 replies, 2 voices, and was last updated 18 years, 6 months ago by
.
-
Posts
-
I’ve been recently frustrated with the delays in the M1 release delays. I probably have been over reacting to what was actually happening. But, I had little in the way of knowing why the milestones kept being moved. I am an impatient sort, but a rational one also. However, I am one to read documentation and information provided about what I’m looking after for, so I had an idea.
Perhaps if the MyEclipse development team provided a blog or something for the community to keep them informed about the state of development, whats holding things up, or what not. This may be too much work for the devs or of no value to anyone else in the community but me so it would not be worth it, just an idea. Maybe even a note on the roadmap when it changes as to why it changed could make the information more transparent.
I agree that our feedback could be better. In fact, we’ve recently started a MyEclipse blog here: http://jroller.com/page/myeclipseblog
It’s still really early in its lifespan so Jens is getting a few evangalism tasks off his chest. Going forward we plan on opening it to other team members for other types of topics.
Oh, and Wayne Parrott, or VP of Product Dev has a blog here: http://jroller.com/page/wparrott
But the problem with that is when the dev team is busy, so is he. It often comes down to the choice of “Work 16 hours” vs “Work 16 hours + do a blog entry”. The blog usually loses.
All that said, we recognize the need to communicate what’s going on a bit better and will try to do so going forward.
@support-scott wrote:
But the problem with that is when the dev team is busy, so is he. It often comes down to the choice of “Work 16 hours” vs “Work 16 hours + do a blog entry”. The blog usually loses.
😀
