Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of kevan.miller@gmail.com
 designates 66.249.82.207 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer;
        b=gCXDbr13HY675iEOKggjIhjDk1Ml69/BbaQ8xJMYDJ+AhIjyI7XiAEeat4k01AmX+x0JqXBYhpHQwuqmk0q/k+xnIO0KHvTTIWD5cnKa9ELV5fgoudI18lWJH6a60qCgXlBdtPtA8sFkmAtu8pjUNynFyv38FDuLlbm4IGDkk90=
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <44CE1771.7010105@hogstrom.org>
References: <44CE1771.7010105@hogstrom.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <1737B732-A866-4F97-BFFF-CD8DEA3DC3C6@gmail.com>
Content-Transfer-Encoding: 7bit
From: Kevan Miller <kevan.miller@gmail.com>
Subject: Re: 1.1.1 Status 2006/07/31
Date: Mon, 31 Jul 2006 12:31:57 -0400
To: dev@geronimo.apache.org


On Jul 31, 2006, at 10:45 AM, Matt Hogstrom wrote:

> Hey everyone,
>
> We're almost there for 1.1.1.  I noticed that people are opeening  
> new JIRA's for 1.1.1 which is great.  However, unless you feel you  
> can get them done before the cut off time please put them in 1.x or  
> 1.2.  I plan on moving all outstanding JIRAs as of the cut off time  
> to the next release.
>
> Alan rightly pointed out a few day slip.  We can easily start a  
> 1.1.2 if people have critical fixes they want to get in.
>
> The branch time remains at *Tuesday, August 1 at 0500 PT*.  On or  
> around this time I will do an SVN copy to branches/1.1.1 and we'll  
> start the final testing, TCK, etc. with the goal to get this out  
> next week.  I announced this time on Friday.
>
> Comments welcome :)

Sounds good.

I'm currently working on TCK issues.

I've moved one of my 1.1.1 Jira's to 1.1.x. Problem needs to be  
fixed, but can be fixed later. Apps can easily (and ought to) avoid  
the problem by closing any Resources they've opened.

The other two 1.1.1 Jira's that are assigned to me are issues having  
to do with the release process. They can be addressed as we're  
releasing 1.1.1.

--kevan