List Info

Thread: Cosmo 0.3: Its time to shut it down and release it.
Cosmo 0.3: Its time to shut it down and release it.
user name
 2006-04-27 19:11:03 

  


  

    I would like to propose that we move as quickly as possible to close down Cosmo 0.3 and get it into the hands of QA as a release candidate. To that end, I am aware of a couple of things that are left to do. Here's my thoughts on how to proceed:

Bug 5339: PUTs take a loooonnng time. 

I recommend that we change the max time range for date expansion from 2050 to 2008 and move forward with that as the fix. In the 0.4 timeframe, we can re-address the problem with a more permanent solution. I would love to take the time to fix this the "right" way, but I think we don't have the time right now and the changes to fix it could be considered risky at this point.

Validation of the migration

I recommend that we set a hard stop on the validation of the migration. I propose that we work on verifying the migration until the end of day on Friday. 


I recommend overall, that we have a hard stop on this release of 5pm PST on Friday 4/28. We will declare a release candidate for QA testing on Monday morning. I would like to be able to declare to QA and Bear that we are ready to move forward with a Release Candidate on Monday morning. 

Any thoughts? We really need to wrap up this release and move on. We're already affecting Scooby's release plans and the longer we wait, the more likely we are to affect other releases as well.

Please respond ASAP with your thoughts. We need to move forward on this ASAP.

Thanks,
--> John


  

  
  
   
     
    

  

    Cosmo 0.3: Its time to shut it down and
release it.
  


  

     user name

     2006-04-27 19:31:56
  


  

    

  


  

    I've reopened Bug 5643 "Cosmo crashes after multiple large event PUTS", this issue needs to be resolved before RC. If the fix is not using the sun JVM anymore then that's fine but we need a fix.

-Mikeal
 
On Apr 27, 2006, at 12:11 PM, John Townsend wrote:

I would like to propose that we move as quickly as possible to close down Cosmo 0.3 and get it into the hands of QA as a release candidate. To that end, I am aware of a couple of things that are left to do. Here's my thoughts on how to proceed:

Bug 5339: PUTs take a loooonnng time. 

I recommend that we change the max time range for date expansion from 2050 to 2008 and move forward with that as the fix. In the 0.4 timeframe, we can re-address the problem with a more permanent solution. I would love to take the time to fix this the "right" way, but I think we don't have the time right now and the changes to fix it could be considered risky at this point.

Validation of the migration

I recommend that we set a hard stop on the validation of the migration. I propose that we work on verifying the migration until the end of day on Friday. 


I recommend overall, that we have a hard stop on this release of 5pm PST on Friday 4/28. We will declare a release candidate for QA testing on Monday morning. I would like to be able to declare to QA and Bear that we are ready to move forward with a Release Candidate on Monday morning. 

Any thoughts? We really need to wrap up this release and move on. We're already affecting Scooby's release plans and the longer we wait, the more likely we are to affect other releases as well.

Please respond ASAP with your thoughts. We need to move forward on this ASAP.

Thanks,
--> John

_______________________________________________
cosmo-dev mailing list
 


  

  
  
   
     
    

  

    Cosmo 0.3: Its time to shut it down and
release it.
  


  

     user name

     2006-04-27 19:31:25
  


  

    
On 4/27/06, John Townsend <townsosafoundation.org>
wrote:

> Bug 5339: PUTs take a loooonnng time.
>
> I recommend that we change the max time range for date
expansion from 2050
> to 2008 and move forward with that as the fix. In the
0.4 timeframe, we can
> re-address the problem with a more permanent solution.
I would love to take
> the time to fix this the "right" way, but I
think we don't have the time
> right now and the changes to fix it could be considered
risky at this point.

i have reservations about this, but i reluctantly agree that
i'd
rather see the release happen.

> Validation of the migration
>
> I recommend that we set a hard stop on the validation
of the migration. I
> propose that we work on verifying the migration until
the end of day on
> Friday.

i'm committing some final changes right now, and then i'm
ready for
this to go to qa.

> I recommend overall, that we have a hard stop on this
release of 5pm PST on
> Friday 4/28. We will declare a release candidate for QA
testing on Monday
> morning. I would like to be able to declare to QA and
Bear that we are ready
> to move forward with a Release Candidate on Monday
morning.

+1. i can spend the rest of today and tomorrow updating the
docs and
getting it all ready.
_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev


  


  

    
  

  
  
   
     
    






 [1-3]











   
 





about | contact  Other archives ( Real Estate discussion Medical topics )