Countersoft's Gemini change log
There appears to be many issues in countersoft's change log (and road map) which come under "won't fix" or "cannot reproduce". Do these issues have to appear under the change log?
There is one issue under 3.01 that should not be there, and 3.01 should be moved to the change log.
Hope this helps....
Nuke AlexS
· 1 |
|
Wednesday, May 28, 2008, 2:09:01 PM |
0
|
Alex, 3.0.1 change log will be issued soon! 3.0.2 will also be documented. 3.1 is a couple of months away and will focus on QA and Requirements. BUT, we will focus on and issue patches frequently to solve bugs and provide minor but useful enhancements. Please bear with us.
|
||||
|
0
|
Hi Harvey Thanks for replying... I'm mainly talking about historical issues that have been dealt with in this particular post. If you actually go to the change log in gemini and look down the issues that have been fixed for various old versions, many have been marked as "duplicate, cannot reproduce, won't fix" etc. I would have thought these issues should be removed from the change log? Thanks... |
||||
|
0
|
Why? These issues were raised and people would like to know the outcome! |
||||
|
0
|
Not sure who you are refering to SaarCohen. Either way the point is that these issues should not be in the change log I would have thought (as actually no change has taken place). No harm keeping them in gemini of course as withdrawn issues. Thanks Alex |
||||
|
0
|
Well, these issues have come to their "final resting place" and should in our view be there. Otherwise it will be hard to find what has happened to them. Where will you show them? You always have the option to purchase the source code if you would like to change this. |
||||
|
0
|
SaarCohen I think you are misunderstanding me here.... I hope.... For instance: http://gemini.countersoft.com/issue/ViewIssue.aspx?id=1189 This is marked as Status = Closed, Resolution = Won't Fix That is fine, but for some reason Fixed for version field is set as "2.1.1", which means it shows up in your change log. I would have thought this value would have to be cleared so it doesn't show up here. Or are you are saying that having withdrawn issues shown as fixed in particular versions of your roadmaps are valid? If you look down your change log there are plenty of other examples like this. I'm only trying to be helpful.. If this is your procedure to leave issues this way come what may, and this is my misunderstanding here, then fair enough, but personally I find this confusing when I'm viewing your roadmap (I'm only interested in looking at fixed issues from this view). Many thanks. |
||||
|
0
|
OK, well I guess I should not have bothered.... Many thanks.... |
||||
|
0
|
No sure what you are after here! Basically, we have decided that the way we use Gemini is by showing all closed issues in the change lo, no matter what was the resolution. As Saar said, this is so we know from what version it was. How many people in your organisation are complaining about this? |
||||
|
0
|
[quote user="MarkWing"] No sure what you are after here! Basically, we have decided that the way we use Gemini is by showing all closed issues in the change lo, no matter what was the resolution. As Saar said, this is so we know from what version it was. [/quote] I noticed that a lot of issues didn't have "fixed for version" set, but nevermind. > How many people in your organisation are complaining about this? No one is complaining about anything, least of all me. I apologise if you guys think I am meddling here. I am sincerely sorry, I'll remember to keep anything I see like this to myself in future. |
||||
|
0
|
FYI I work on the dotnetnuke project, I am hoping you guys are going to be upgrading us to 3.01 soon... |
||||
|
0
|
We welcome criticism and suggestions to make Gemini better. In this case we just did not agree with your view. At the end of the day it is up to each Gemini admin to decide what will go with the version. We decided that all closed issues (no matter the resolution) will be associate with the released version. |
||||
|