I am going to include the lack of a release manager for 3.0 in the board
report, and assign myself an action item to fix it.
At this point I think my best bet is to appeal on the
d...@community.apache.org mailing list for a mentor who is familiar with
the release process to guide me through the steps. However, I am very
open to alternative suggestions.
On 8/8/2015 8:22 AM, Patricia Shanahan wrote:
Peter? Anyone?
I have time, but not the knowledge. I would be willing to be release
manager provided at least one person who knows how it is done will
provide a lot of step-by-step guidance.
On 8/8/2015 7:21 AM, Bryan Thompson wrote:
Not really I am afraid. I am quite heavily committed on several projects
right now. I have done applications development with river, but I am not
familiar with the historical river project structure in any depth and
have
never done development on river itself. And I have never participated
in an
Apache project release. I am just not a good candidate for this.
Thanks,
Bryan
On Saturday, August 8, 2015, Patricia Shanahan <p...@acm.org> wrote:
Bryan,
Are you able and willing to act as release manager for 3.0?
On 8/6/2015 11:56 AM, Bryan Thompson wrote:
Just release to encourage people to use it. +1 on release.for me.
On Aug 6, 2015 2:55 PM, "Patricia Shanahan" <p...@acm.org> wrote:
Would it be useful to tag it as a 3.0 beta release initially, or
just go
to 3.0 and add point releases as needed?
I will vote in favor of releasing it either way.
On 8/6/2015 9:55 AM, Bryan Thompson wrote:
Or just release it. If problems emerge, people can report them and
they
can get fixed. There is a known reliable release now. Let the
community
vote by migrating their code.
Bryan
On Thu, Aug 6, 2015 at 12:41 PM, Patricia Shanahan <p...@acm.org>
wrote:
As far as I can tell, the main remaining release blocker it
getting more
people to test in more environments. Perhaps we should put out an
appeal
on
u...@river.apache.org?
On 8/6/2015 9:33 AM, Bryan Thompson wrote:
Maybe it would be good to say a few words about the release goals
for
3.0?
I.e., 3.0 provides a deep refactoring that address performance,
concurrency
and scaling issues. Significant progress has been made towards the
3.0
release target. X new tests have been developed for this release.
The
remaining blockers for a release are ....
