Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (nike.apache.org: domain of jukka.zitting@gmail.com
 designates 74.125.82.50 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAOFYJNbhjkhYvytyJM-Z_uv5LpC7EsfpTAsSwhLzjz8UmBUxVw@mail.gmail.com>
References: 
 <CAOFYJNbhjkhYvytyJM-Z_uv5LpC7EsfpTAsSwhLzjz8UmBUxVw@mail.gmail.com>
From: Jukka Zitting <jukka.zitting@gmail.com>
Date: Wed, 7 Mar 2012 09:25:53 +0100
Message-ID: 
 <CAOFYJNaKGmTXfUYhhB40NKaDQYhoNYnkzZi5QDnkqDEAZD2SqQ@mail.gmail.com>
Subject: Re: Setting up Oak (Was: [RESULT] [VOTE] Codename for the jr3
 implementation effort)
To: Jackrabbit Developers <dev@jackrabbit.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

Hi,

On Tue, Mar 6, 2012 at 1:00 PM, Jukka Zitting <jukka.zitting@gmail.com> wrote:
> The oak-dev@ mailing list should follow up shortly, see INFRA-4514 [1].

The list is ready now, you can subscribe by sending a message to
oak-dev-subscribe@jackrabbit.apache.org. I suggest we move discussion
about Oak to the new list gradually over the next few days as
interested people get subscribed. I'll change the Jira notifications
for OAK to go to the new list at the end of today.

The main rationale for using a separate mailing list is that the Oak
codebase is a fundamentally different repository implementation than
Jackrabbit 2.x (a "revolution" in Stefano's terms), and a separate
list should help make that more obvious and help prevent confusion
like in the other thread where people were jumping to wrong conclusion
about identifiers based on current Jackrabbit design.

BR,

Jukka Zitting