IMPORTANT: Tracker cleanup
As it have been previously discussed we're trying to get rid of tracker
noise and migrate to another issue control system (JIRA).
This is how the process will go on:
1. There's two weeks starting now EAPers are encouraged to place their
votes against tracker issues they feel important or making sense.
2. It would be great if issues that aren't any longer have any sense
will loose their votes.
3. As two weeks are over (Dec, 7th) the current issue tracher at
http://www.intellij.net/tracker/IDEA will go into read-only mode and all
issues that have non-zero votes against them will be ported to new issue
tracker.
4. Some additional manual processing of the issues to be ported will
take place to ensure there's no duplicates and requests are formulated
clearly.
Thanks for understanding and hope for a cooperation.
--
Maxim Shafirov
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"
请先登录再写评论。
Awsome! Is there an exchange rate to US$? :)
Amnon I. Govrin wrote:
Yep, 0.00$ per vote :) And 0 votes per 1$ the other way. Just to make
sure no one going to divide by zero to get unlimited votes.
--
Maxim Shafirov
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"
Maxim,
Maxim,
I hope you won't give too much importance to the number of votes authors
spent on their bugs and requests, when picking Irida candidates : by
definition, the most prolific posters have less to spend on individual bugs.
Alain
I'd hope that in the new tracker, everything starts off with 0 votes, another 'fresh' start.
Hani Suleiman wrote:
Quite right. The number of votes in the tracker won't mean anything when
migrating. Only >0 criteria matters. After migrating to JIRA voting will
start from 0 indeed. And as it have been already mentioned JIRA allows 1
vote per request per person. So we do measure voters rather than votes.
--
Maxim Shafirov
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"
WOHOO! Hopefully this will reflect a more accurate desire/support by the
community for a certain feature... Though that's not necessarily always a
good thing either. :)
Will there be a limit on how many issues we can vote for?
R
On 11/24/04 4:26 PM, in article co2uc7$bv0$1@is.intellij.net, "Maxim
Shafirov (JetBrains)" <max@jetbrains.com> wrote:
>> I'd hope that in the new tracker, everything starts off with 0 votes, another
>> 'fresh' start.
Maxim ,
>
I guess you won't force to revote again, and will init the transfered
bugs/request this way:
JIRA nof votes <-- Tracker nof voteRs
Alain
Robert S. Sfeir wrote:
>WOHOO! Hopefully this will reflect a more accurate desire/support by the
>community for a certain feature... Though that's not necessarily always a
>good thing either. :)
With hundreds (? thousands) of submitted or open features, you can't
expect the number of voters to represent anything but the feature
visibility, at the time of its publication. In that context, I think
that, for most features, spontaneous voting is a waste of time.
One workaround would be for JetBrains, during the EAP, to communicate
better with us, and work in short waves/cycles, like this :
JetBrains
1/ publishes a list of low/medium and high level subjects on which
they plan to work in the coming months (ex: junit, Ant, Ctrl-F12,
compiling, EJBeditor, EJBdeploying, etc..)
, and ask that
Bug authors
2/ with related features regroup and push them forward, and clarify
if necessary
JetBrains
3/ collate all the features, by group,
4/ digest them, and publish a short description of their plan/roadmap
Bug authors
5/ comment the roadmap, for a few days (2-3)
Everybody
6/ the public comments the roadmap, for 1 week
JetBrains freezes the requests, and publish a quasi-fixed and official
roadmap
As the EAP is quite long, there would be many cycles like this during
the EAP.
I think this would remove a big part of the noise and chaos (the
uninterrupted features request shower) that characterizes each EAP.
Alain
Maxim Shafirov (JetBrains) wrote:
>> http://www.intellij.net/tracker/idea/viewSCR?publicId=35247, after
>
What about bugs and features submitted by Jetbrains themselves?
Almost all your (Maxim's) SCR's have zero votes (40 out of 57 open or
submitted). Some examples:
http://www.intellij.net/tracker/idea/viewSCR?publicId=40264
http://www.intellij.net/tracker/idea/viewSCR?publicId=39117
http://www.intellij.net/tracker/idea/viewSCR?publicId=38437
I didn't realize the apparent importance you place upon votes until a
little over two weeks ago, when I read this message by you:
http://www.intellij.net/forums/thread.jsp?forum=28&thread=114539#3414137
In which you ask "please note this is not low votes but ZERO votes. Does
that mean even submitter does not care?". I would have thought that the
interest the submitter has is already demonstrated by his or hers
willingness to submit a bugreport, which takes a lot more effort than a
simple vote.
I have always found it natural to not vote for my own issues. You
apparently don't vote for your own issues either.
Are Jetbrains SCR's automatically transferred? Do you vote yourself for
issues you find important or do you leave it up to the community to vote
and thus transfer your SCRs?
Best regards,
Bas
ps. I do not mean to sound critical or offend, I'm just curious.
Well, I'll probably transfer my request manually (as well as other team
member request). It either equal work for me (voting or tranferring).
BTW, the submitter has no ability to vote for own requests in JIRA.
--
Maxim Shafirov
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"
Maxim Shafirov (JetBrains) wrote:
Ok, thanks for the info.
Much better thanks.
Bas