Received: by 10.236.170.198 with SMTP id p46mr3697145yhl.8.1323329348781;
        Wed, 07 Dec 2011 23:29:08 -0800 (PST)
X-BeenThere: joomla-dev-cms@googlegroups.com
Received: by 10.101.212.35 with SMTP id o35ls3652747anq.2.gmail; Wed, 07 Dec
 2011 23:29:06 -0800 (PST)
Received: by 10.236.170.198 with SMTP id p46mr3697068yhl.8.1323329346645;
        Wed, 07 Dec 2011 23:29:06 -0800 (PST)
Received: by 10.236.170.198 with SMTP id p46mr3697067yhl.8.1323329346631;
        Wed, 07 Dec 2011 23:29:06 -0800 (PST)
Return-Path: <jooml...@googlemail.com>
Received: from mail-yx0-f186.google.com (mail-yx0-f186.google.com [209.85.213.186])
        by gmr-mx.google.com with ESMTPS id v43si1233545yhm.5.2011.12.07.23.29.06
        (version=TLSv1/SSLv3 cipher=OTHER);
        Wed, 07 Dec 2011 23:29:06 -0800 (PST)
Received-SPF: pass (google.com: domain of jooml...@googlemail.com designates 209.85.213.186 as permitted sender) client-ip=209.85.213.186;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jooml...@googlemail.com designates 209.85.213.186 as permitted sender) smtp.mail=jooml...@googlemail.com
Received: by yenr9 with SMTP id r9so1604272yen.23
        for <joomla-dev-cms@googlegroups.com>; Wed, 07 Dec 2011 23:29:06 -0800 (PST)
Received: by 10.236.174.4 with SMTP id w4mr626203yhl.10.1323329346586;
        Wed, 07 Dec 2011 23:29:06 -0800 (PST)
Date: Wed, 7 Dec 2011 23:29:05 -0800 (PST)
From: brian teeman <jooml...@googlemail.com>
Reply-To: joomla-dev-cms@googlegroups.com
To: joomla-dev-cms@googlegroups.com
Message-ID: <16476584.1196.1323329345564.JavaMail.geo-discussion-forums@yqiw17>
In-Reply-To: <24921708.15.1323318527181.JavaMail.geo-discussion-forums@yqjw36>
References: <CADPtAkTAvYi423c_t6aM47se6nkO5Jd=rEmaAXMfycSK=icOJQ@mail.gmail.com>
 <24921708.15.1323318527181.JavaMail.geo-discussion-forums@yqjw36>
Subject: Re: Proposal to push back future releases by one month or so
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_1194_7550101.1323329345561"

------=_Part_1194_7550101.1323329345561
Content-Type: multipart/alternative; 
	boundary="----=_Part_1195_25240174.1323329345562"

------=_Part_1195_25240174.1323329345562
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

We are a global project and there will always be times of the year which 
are too busy for one nationality or other so we are never going to find a 
quiet time for everyone . 

Having said that we also have to acknowledge that the December/January 
period is "busy" for one reason or other for the majority, if not me. 8 + 
years of experience tells me that people's available time over this period 
is severely limited.

Pushing back by 1 month therefore gets my vote but as Mark said we really 
do want to stick to the January release for the next CMS release so how 
about aiming for Jan 31. 

------=_Part_1195_25240174.1323329345562
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

We are a global project and there will always be times of the year which are too busy for one nationality or other so we are never going to find a quiet time for everyone .&nbsp;<div><br></div><div>Having said that we also have to acknowledge that the December/January period is "busy" for one reason or other for the majority, if not me. 8 + years of experience tells me that people's available time over this period is severely limited.</div><div><br></div><div>Pushing back by 1 month therefore gets my vote but as Mark said we really do want to stick to the January release for the next CMS release so how about aiming for Jan 31.&nbsp;</div>
------=_Part_1195_25240174.1323329345562--

------=_Part_1194_7550101.1323329345561--