On Tue, Jan 29, 2013 at 9:39 AM, Ian Lynagh wrote:

On Tue, Jan 29, 2013 at 09:19:36AM +0000, Simon Peyton-Jones wrote:

...

| The discussion about replacing abbot seems to be achieving consensus. | There's no urgency, but if it seems to taper out again then I'll try | prodding the committee to put the plan into action.

What *is* the consensus?

To get a Hetzner server, and run a bunch of VMs on it for the different services.

I missed this discussion, but as an owner of a Hetzner machine I must say it sounds like a good idea to me. Really nice machines. -- Johan

+1 re upgrading trac. On Tue, Jan 29, 2013 at 12:11 PM, David Terei wrote:

If we are migrating the GHC trac would it also be possible to upgrade it to 1.0? The current version 0.11.6 is fairly old now and 1.0 contains a few improvements that would be nice. (e.g., support for multiple git repos so we could see patches to libraries as well).

Cheers, David.

On 29 January 2013 09:39, Ian Lynagh wrote:

...

On Tue, Jan 29, 2013 at 09:19:36AM +0000, Simon Peyton-Jones wrote:

...

| The discussion about replacing abbot seems to be achieving consensus. | There's no urgency, but if it seems to taper out again then I'll try | prodding the committee to put the plan into action.

What *is* the consensus?

To get a Hetzner server, and run a bunch of VMs on it for the different services.

I think everyone's agreed on that, but there's some discussion about how best to handle backups.

...

We should get on with this. It bit several times recently, and we don't want to wait until it becomes really serious! (And it looks bad.)

Replacing abbot isn't related to the recent problems with abbot. We want to replace it because the hardware is a few years old and out of warranty, but the recent problems were software issues and would probably affect the replacement in the same way.

Thanks Ian

_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs

_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs

Most of the new features in 1.0 are promotions of plugins (e.g., git support is now integrated, and the source code browser is branch aware) and macros (e.g. TracBatchModify and Workflow). They claim to have updated the interface too. But we can get most of this with 12.x plus some local installs. Going with 12,2 (or even 12.5. latest stable release of 12.x, the long-term support line) is fine by me too. /A On Tue, Jan 29, 2013 at 12:36 PM, Ian Lynagh wrote:

Hi Andy,

On Tue, Jan 29, 2013 at 12:18:48PM -0800, Andy Adams-Moran wrote:

...

+1 re upgrading trac.

What new features in particular would you like?

Thanks Ian

On 29 January 2013 12:36, Ian Lynagh wrote:

Hi Andy,

On Tue, Jan 29, 2013 at 12:18:48PM -0800, Andy Adams-Moran wrote:

...

+1 re upgrading trac.

What new features in particular would you like?

I'd mostly like support for multiple Git repos as I already mentioned. As others have mentioned 0.12x seems to have this so that's great. The 1.0 release highlights according to the trac team are: * Refreshed user interface * Git support * Branching structure displayed in the revision log * Ticket batch modification support All seem pretty nice (although new UI would take some adjusting and I dont think its that much of an improvement over 0.11 / 0.12 design). Git support may simply be promoting the plugin as Andy mentioned, not sure if performance is improved over 0.12. Batch modification may be something useful for you Ian (or perhaps the Simons) but otherwise I don't think anyone else.

Thanks Ian

_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs

Unfortunately, I can't find any timescale for the release anywhere, but it's currently frozen. It's frozen for about 7 months now. Debian is released "When It's Done" and I think the only timescale you can find is the number of release-critical bugs:

http://bugs.debian.org/release-critical/ Wheezy will be released when the green line gets to zero (no bugs). Judging from how it goes so far I'd say about 4 more months, but this is a very rough guess. Still, waiting for a new release sounds like a good idea (that's what I'm doing). Janek