Mailing-List: contact mime4j-dev-help@james.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mime4j-dev@james.apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Message-ID: <1402313783.27071.2.camel@ubuntu>
Subject: Re: Release 0.8.0?
From: Oleg Kalnichevski <olegk@apache.org>
To: mime4j-dev@james.apache.org
Date: Mon, 09 Jun 2014 13:36:23 +0200
In-Reply-To: 
 <CAGHyZ6K6=Bw5_o9jM9-ysSN-ptVhZaU_zESRo4XHvn-EGPsarA@mail.gmail.com>
References: 
	<CAGHyZ6K6=Bw5_o9jM9-ysSN-ptVhZaU_zESRo4XHvn-EGPsarA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Fri, 2014-06-06 at 10:14 -0500, Sean Busbey wrote:
> Hi!
> 
> It's been ~year since I last saw a 0.8.0 release brought up. Any chance we
> could get one soon?
> 
> If trunk is still not stable enough, could someone point me towards what
> needs to be done? e.g. testing additions or feature work?
> 
> In particular I'm looking to get the mbox iterator into a released artifact.
> 

Since no one else responded here is my personal take on the situation.
0.8 (trunk) is nowhere near being release ready and is unlikely to get
there any time soon given no one is currently working on it.

The only practical solution to getting the mbox iterator functionality
into an official release is to merge it to the 0.7 branch and release it
from there.

Oleg