Conductor v13.11.14 is being released today. It mostly contains bugfixes and upgrades to several libraries that Conductor uses.
This weekend, the Conductor admin and public sites will be unavailable from 11PM on Saturday November 9th to approximately 3AM on Sunday November 10th for scheduled maintenance.
Sunday, October 13 from 2-6 a.m.
This weekend Conductor will be taken down for maintenance. During that time our hosting provider will be moving our servers to new hardware to address some recent server failures. All Conductor sites and admins will be unavailable during the outage. We apologize for any inconvenience this may cause.…
Conductor v13.9.27 will be released shortly. It features a permissions bugfix.
Conductor v13.9.25 will be released today. It fixes several minor bugs.
Conductor v13.9.24 has been deployed. It fixes a bug in the pages section of the admin.
Conductor v13.9.23 will be deployed today, with added support for author-specific news listings and better image processing.
Starting at 11:30pm on Friday, September 13, Conductor and all sites will be down for extended maintenance. During this time, our hosting provider will be moving the physical server that hosts Conductor to a new data center. Total downtime will be approximately six hours.
We apologize for any inconvenience this may cause.…
Conductor v13.8.15 will be deployed tomorrow. It's a minor release.
Scheduled for 7:30am on Thursday, August 15, 2013, this release will cause minor downtime when deployed. We expect this downtime to be less than 5 minutes, but during that time the admin will be unavailable. Public sites should not be affected.…
The v13.8.8 release had some minor errors in it, which have been resolved with two patches.
Conductor v13.8.8 will be released Thursday, August 8. 10 minutes of downtime is expected.
Conductor v13.7.19 is released today. It's a minor release.
We are introducing a new release numbering format. Going forward, release names will follow the format "v<year>.<month>.<day>", based on the date that the deploy is performed. If multiple deploys are performed in a single day, a "-p<n>" will be appended to the release number: "p" for "patch," and "n" as the patch number for that day's release.
Following the hardware upgrades that occurred before break, we have put into place several changes to Conductor and upgrades to the server between last Friday (the 4th) and this morning at 6 AM. These updates should result in dramatic performance improvements for Conductor. We have other upgrades in the works to further improve performance in the coming months.…
Thank you for your patience as we upgrade Conductor's server structure. Conductor has seen rapid growth—we recently launched our 300th site, and nearly 1,300 members of the Notre Dame community are trained Conductor users. To add to that, external traffic is at an all-time high.
With growth comes the need for infrastructure upgrades.…
UPDATE: The maintenance has been moved to Sunday, December 16 at 1pm.
In a push to reduce recent Conductor slowness, on Saturday, December 15 Conductor will experience two periods of downtime for a scheduled hardware upgrade. At 1pm EST and 3pm EST Conductor will be taken off-line by our hosting provider to upgrade the server hardware. During this time period, websites will be unavailable to the public and site admins will not have the ability to make changes.…
Conductor and all associated sites were unavailable today from approximately 10:10am to 11:22am. The server experienced a resources issue which caused the server to lock-up requiring a hard reboot. We will be working with our provider to find solutions to prevent this from happening again.
We apologize for any inconvenience this outage may have caused.…
On Sunday 9am June 3rd, 2012 we will be updating Conductor's servers. These updates will likely result in an hour or more of extended downtime. If you have any questions or concerns or really can't afford for your site to be offline at 9am on a Sunday during the summer, please contact firstname.lastname@example.org.
This morning, at approximately 3:45am, Conductor's database server stopped responding. At approximately 6:45am, the database server was brought back up.
In the lead up to the outage, no information was lost. During the outage, any updates via the Conductor admin may not have been saved.
I have investigated the cause and have made some initial adjustments to ensure that this particular problem does not happen again.…
On February 5th, 2012 at 8am, we will be performing server updates to Conductor. The nature of these updates may result in extended system downtime.
The expected down time is at least an hour, though we are hoping the maintenance can be completed in less time.