Re: [Treebase-devel] Scheduling Production Build

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

We have manually deployed the latest version from Development to Production.  Let us know if you have questions.

Thanks, David

From: David Palmer
Sent: Friday, July 29, 2011 9:06 AM
To: 'tre...@li...'
Cc: 'Mattison Ward (mw225)'; Hilmar Lapp
Subject: RE: Scheduling Production Build

We have restored the state prior to the upgrade.  The TreeBASE production system is again online.

Thanks, David

From: David Palmer
Sent: Friday, July 29, 2011 8:50 AM
To: tre...@li...<mailto:tre...@li...>
Cc: Mattison Ward (mw225); Hilmar Lapp
Subject: RE: Scheduling Production Build

The production TreeBASE build failed this morning.  We are actively working on restoring services to TreeBASE production.

Thanks, David

From: David Palmer
Sent: Thursday, July 28, 2011 11:08 AM
To: tre...@li...<mailto:tre...@li...>
Cc: Mattison Ward (mw225)
Subject: Scheduling Production Build

A request has been made to re-build the Production instance of TreeBASE.  This update is being schedule for Friday, July 28, 2011.  Please let me know if you have questions/concerns.

Thanks,
David Palmer
NESCent
919 668 6520

Thu Jul 28 00:22:51 2011 William Piel - Ticket created [Reply<http://help.nescent.org/Ticket/Update.html?id=11506&QuoteTransaction=215965&Action=Respond>] [Comment<http://help.nescent.org/Ticket/Update.html?id=11506&QuoteTransaction=215965&Action=Comment>][Forward<http://help.nescent.org/Ticket/Forward.html?id=11506&QuoteTransaction=215965>]
Subject:

Important bug fix for TreeBASE

Date:

Thu, 28 Jul 2011 00:22:46 -0400

To:

"NESCent Issue Tracker (help)" <he...@ne...<mailto:he...@ne...>>

From:

William Piel <wil...@ya...<mailto:wil...@ya...>>

Download (untitled)<http://help.nescent.org/Ticket/Attachment/215965/342736/> / with headers<http://help.nescent.org/Ticket/Attachment/WithHeaders/342736>
text/plain 309b

Hi,

Harry made an important fix to revision 934. The bug is preventing people from removing trees from analyses, and it also seems capable of corrupting data. I've tested Harry's fix on dev and it seems to solve the problem. So if we could have a push to production, that would be great.

thanks,

Bill