athlonkmf Posted March 15, 2007 Share Posted March 15, 2007 Simple question:The bugs that were marked as fixed after the initial release of 2.2.2, are they already implemented in the current downloads?Or will they be really fixed when 2.2.3 comes out? Link to comment Share on other sites More sharing options...
Mark Posted March 15, 2007 Share Posted March 15, 2007 With 2.2.3Basically they fix all the bugs, then after a lot of bugs (or a major bug) has been fixed, the next version is released.So any bugs marked 'fixed' before 2.2.2 came out are fixed in 2.2.2 - those marked as 'fixed' after 2.2.2 came out will be fixed in 2.2.3The versions never change, so if I download 2.2.2 now it will be the exact same as if I downloaded it a week ago. Link to comment Share on other sites More sharing options...
Michael Posted March 15, 2007 Share Posted March 15, 2007 The versions never change, so if I download 2.2.2 now it will be the exact same as if I downloaded it a week ago.Not necessarily. Sometimes there will be bugs in the very first downloads of a new version that they fix and update the download with. Link to comment Share on other sites More sharing options...
Mark Posted March 16, 2007 Share Posted March 16, 2007 Yes, bar a few things like missed files in the update pack. Assuming my copy of 2.2.2 works, there is no need to redownload it Link to comment Share on other sites More sharing options...
W13 Posted March 17, 2007 Share Posted March 17, 2007 Not necessarily. Sometimes there will be bugs in the very first downloads of a new version that they fix and update the download with.Yea- like major bugs, security flaws, etc. Link to comment Share on other sites More sharing options...
Digi Posted March 17, 2007 Share Posted March 17, 2007 No, that isn't what Michael meant. For those extremes they'll release it as another version to prevent confusion. Especially in the case of new security exploits. Link to comment Share on other sites More sharing options...
bfarber Posted March 19, 2007 Share Posted March 19, 2007 On rare occasions, we will create an update pack, test it for a while, and then release it - only to find a file is missing in the update pack, or there is an obvious issue we did not notice that was reported to us right away when the update is made available. In those cases, it makes better business sense to go ahead and update the download to fix the problem, limiting the number of customers affected (100 is better than 1000, for example).This does not happen extremely often, and since 2.1.5 or so we have worked hard to limit it from happening at all, due to the confusion it can cause for both customers and our technical support staff.Generally if it happens, and an issue is reported, we will note that the package was updated and you can redownload it to correct an issue.To answer the original question, if a bug is categorized as 2.2.2 and marked fixed, it likely will be fixed for 2.2.3. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.