Re: [flexcoders] Flex 2 patch timeline

[hank williams]

Given what they are doing, this might be hard as they are making changes to accomodate the mac that I am sure are often causing "breaking the build". That is just a guess of course but if the mac support is as hard as I think it is they would have to fork the build in order to do this. Oh and the other problem is that the *would* have to support it.
But that said, its not a bad idea. Its just that the devil is in the details.RegardsHankOn 8/30/06, Tom Lee <
[EMAIL PROTECTED]> wrote:
















I figure Adobe Labs would be a great
middle ground for this sort of thing – Put the fixes out there for the
early adopters (with the appropriate warnings) and then make official releases
less often.  After all, it's not like these fixes are Player revisions.

 









From: 
flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] 
On Behalf Of hank williams
Sent: Wednesday, August 30, 2006
4:12 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Flex 2
patch timeline



 

 



On 8/30/06, Jack
Caldwell <[EMAIL PROTECTED]>
wrote:






Jeff:


 


I fully understood what
Matt was saying.  That's just it . . . . it is not a top priority.


 


The issue is that Adobe
is fixing the bugs, but not releasing them.








Jack,

With any big software project, there are **always** bugs. Typically hundreds.
You *never* get down to zero and rarely even into the dozens. The question is
how many of them are there and how important are they. You cant put a new
release out every time there is a bug. So you have to decide when a good time
to do  it is. If there are major and important bugs to fix, you put a
release out. But you cant do that weekly. Thats why its important for them to
know if there are any showstopper or really important bugs. 

So Matt's question was important. Are there any bad bugs that they dont know
about? It makes total sense to me, if there are no major bugs, to wait and put
out a new release in 4 or 5 months. New releases are organizationally
traumatic. And they are also not risk free. It is always possible to introduce
new bad bugs while fixing old not so important ones. So waiting a while and
being sure everything is right with a full QA cycle is not a bad thing at all.
Doing that around a major change like mac support (which will also effect the
windows version because its the same codebase) seems like the right thing to do
if there are no major problems. 

Regards
Hank



 

















__._,_.___





--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com








   



    


  
  
    SPONSORED LINKS
  
          
                  
            
        Software development tool
      
                      
        Software development
      
                      
        Software development services
      
              
                        
            
        Home design software
      
                      
        Software development company
      
                    
           
  







  
  
  YAHOO! GROUPS LINKS



   Visit your group "flexcoders" on the web. 
   To unsubscribe from this group, send an email to: [EMAIL PROTECTED] 
   Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.



  






__,_._,___