Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Message-ID: <571FAAD8.2090009@apache.org>
Date: Tue, 26 Apr 2016 13:52:24 -0400
From: Josh Elser <elserj@apache.org>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: Commons Developers List <dev@commons.apache.org>
Subject: Re: [VFS] 2.1 Release Plan
References: <571E6A9B.40005@apache.org>
 <CACZkXPxzdQ9=LBVJa6JCeGjFn9KO9buqCXh6LTthdsazKopj3A@mail.gmail.com>
 <CACmp6kq1q3PrfKBWOCwDSB29T+pKeQgsuGybP2D9JHJh1WY-kw@mail.gmail.com>
 <571F6FB1.9030503@apache.org>
In-Reply-To: <571F6FB1.9030503@apache.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Best as I can see, Benson was able to do the commons-io 2.5 release 
after someone else added his key to the KEYS file (because had some 
separate karma being applied to it which was not included in the 
universal-commit change).

Consider this my formal volunteer offer to be RM for commons-vfs 2.1.

Josh Elser wrote:
> Thanks Matt and Gary.
>
> I do recall seeing the asf-wide note that my commit-bit also applies to
> commons-*. Thanks for bringing that up. Specifically though, I am only
> interested in cutting a release -- if we can get a new release cut that
> we can use downstream, that increases the likelihood that I will have
> more things to contribute back :)
>
> I'll pull up the thread in the archives and get back to ya'll with any
> questions I have after that.
>
> - Josh
>
> Matt Sicker wrote:
>> It's from the thread called "Whatever happened to commons-io 2.5?" A few
>> people stepped up to give the necessary permissions and committed his GPG
>> key.
>>
>> On 25 April 2016 at 17:10, Gary Gregory<garydgregory@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> Agreed, VFS 2.1 has been too long in the making. We can release ASAP
>>> without fixing more bugs IMO. RERO and all.
>>>
>>> As an Apache committer, your are also an Apache Commons committer, so
>>> feel
>>> free to create JIRAs, fix bugs and so on.
>>>
>>> There might be some karma issues with a non-PMC member performing a
>>> release, and I think we just went through this (sorry, I'm in
>>> settling in a
>>> new house, not much time to dig in the ML archives).
>>>
>>> Does anyone recall?
>>>
>>> Gary
>>>
>>>
>>>
>>> On Mon, Apr 25, 2016 at 12:06 PM, Josh Elser<elserj@apache.org> wrote:
>>>
>>>> Hi all,
>>>>
>>>> There are presently 171 resolved issues sitting in commons-vfs2
>>>> 2.1-SNAPSHOT, with 4 outstanding (none of which look like blockers to
>>> me).
>>>> The lack of any release of commons-vfs2 in years has been a big problem
>>>> downstream. This past weekend, I was again annoyed by bugs that have
>>>> been
>>>> fixed (but not release) which is spurring me to take some action. There
>>>> have been emails reaching back as far as 2014 asking when the next
>>> release
>>>> might be, not to mention the fact that vfs-2.0 was released in 2011
>>>> (!).
>>>>
>>>> History aside, I'm reaching out today to:
>>>>
>>>> 1) See if anyone on the PMC has the cycles to volunteer as RM.
>>>> 1a) If not, how can you empower me (or others) to make the release on
>>>> your behalf.
>>>> 2) Understand, specifically, what (if any) roadblocks exist to release
>>>> this version.
>>>>
>>>> Thanks.
>>>>
>>>> - Josh
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>>
>>>
>>> --
>>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>>> Java Persistence with Hibernate, Second Edition
>>> <http://www.manning.com/bauer3/>
>>> JUnit in Action, Second Edition<http://www.manning.com/tahchiev/>
>>> Spring Batch in Action<http://www.manning.com/templier/>
>>> Blog: http://garygregory.wordpress.com
>>> Home: http://garygregory.com/
>>> Tweet! http://twitter.com/GaryGregory
>>>
>>
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org