On Fri, Dec 14, 2012 at 12:52 AM, Gwern Branwen wrote:

On Thu, Dec 13, 2012 at 5:11 AM, Carsten Mattner wrote:

...

From my perspective darcs head for both xmonad and XMonadContrib is in good shape for a release. Let's cut a release.

As usual, I have no objection to a release on a schedule quicker than 'once a decade'...

Let's do it then. What's the process? Any critical open tickets with suggested patches to consider?

On Fri, Dec 14, 2012 at 10:22 PM, Carlos López Camey wrote:

2012/12/14 Carsten Mattner :

...

On Fri, Dec 14, 2012 at 12:52 AM, Gwern Branwen wrote:

...

On Thu, Dec 13, 2012 at 5:11 AM, Carsten Mattner wrote:

...

From my perspective darcs head for both xmonad and XMonadContrib is in good shape for a release. Let's cut a release.

As usual, I have no objection to a release on a schedule quicker than 'once a decade'...

Let's do it then. What's the process?

Any critical open tickets with suggested patches to consider?

Hello Carsten, I've code I'd like to remove before a possible release. The patch is attached with the following summary:

I'll let X.A.Launcher stay as an example of a prompt with multiple modes. This patch removes LocateMode and LocateRegexMode which were used to search file paths.

They are not optimal, they're slow and I'm working on another solution which involves another dependency. The dependency is an experimental indexer I'm writing, I believe that places my efforts outside the scope of xmonad-contrib.

Sounds like a good idea to me.

2012/12/15 adam vogt :

On Fri, Dec 14, 2012 at 4:22 PM, Carlos López Camey wrote:

...

Hello Carsten, I've code I'd like to remove before a possible release. The patch is attached with the following summary:

I'll let X.A.Launcher stay as an example of a prompt with multiple modes. This patch removes LocateMode and LocateRegexMode which were used to search file paths.

They are not optimal, they're slow and I'm working on another solution which involves another dependency. The dependency is an experimental indexer I'm writing, I believe that places my efforts outside the scope of xmonad-contrib.

Hi Carlos,

You also wanted to remove spawnWithActions with your patch? As it stands, it isn't used or exported.

Also on the side, the orElse1 you define as part of that function is a specialized version of Control.Monad.msum which seems to be in base.

-- Adam

Hello Adam, thanks for making sure my mistakes don't go through and for the msum pointer. On haskell-cafe I found this one too, not long ago: Prelude> import Control.Applicative Prelude Control.Applicative> :t (<|>) (<|>) :: Alternative f => f a -> f a -> f a Prelude Control.Applicative> Just 7 <|> Nothing Just 7 Prelude Control.Applicative> Nothing <|> Nothing Nothing Prelude Control.Applicative> Nothing <|> Just 1 Just 1 Please find attached the patch that removes spawnWithActions. cheers

This 1-patch bundle was just applied to http://code.haskell.org/XMonadContrib: 20121214211230 c.lopez@kmels.net * Removes LocateMode and LocateRegexMode from XMonad.Actions.Launcher -- This message was brought to you by DarcsWatch http://darcswatch.nomeata.de/repo_http:__code.haskell.org_XMonadContrib.html...

On Sat, Dec 29, 2012 at 7:24 PM, Joachim Breitner wrote:

Hi,

Am Freitag, den 14.12.2012, 11:28 +0100 schrieb Carsten Mattner:

...

On Fri, Dec 14, 2012 at 12:52 AM, Gwern Branwen wrote:

...

On Thu, Dec 13, 2012 at 5:11 AM, Carsten Mattner wrote:

...

From my perspective darcs head for both xmonad and XMonadContrib is in good shape for a release. Let's cut a release.

As usual, I have no objection to a release on a schedule quicker than 'once a decade'...

Let's do it then. What's the process?

good question, but I wonder what the answer is, whose it is to give and especially why it has not been given yet.

From what I see I believe it's decided with a consensus after whoever does the required work of going through the bug tracker, write Changelog, NEWS, and release notes.

What's holding up a release with current darcs before the year ends? Does anybody have concerns with the reliability or backwards compatibility of the code found in darcs as of today?

On Mon, 31 Dec 2012 17:31:25 +0100, adam vogt wrote:

On Sat, Dec 29, 2012 at 1:30 PM, Carsten Mattner wrote:

...

From what I see I believe it's decided with a consensus after whoever does the required work of going through the bug tracker, write Changelog, NEWS, and release notes.

What's holding up a release with current darcs before the year ends? Does anybody have concerns with the reliability or backwards compatibility of the code found in darcs as of today?

Hi Carsten,

There might be some easy things to fix to get xmonad & contrib to build with older ghcs. For example, things like "import Control.Exception" can easily be changed to "import Contol.Exception.Extensible", if that's the only change necessary to maintain compatibility with something as old as ghc-6.12.

If it's trivial changes to keep it compatible, I'm all for it in the name of not breaking builds for users or packagers.

I've listed some highlights for the release I'll hopefully get out today: http://www.haskell.org/haskellwiki/Xmonad/Notable_changes_since_0.10

Adam, that's great news. There's a tiny typo: "issue issue"

Other things to remember for the release are listed in: http://code.haskell.org/xmonad/TODO