openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Albert Lee <>
Subject Re: OpenJPA 2.2.0 release plan
Date Sat, 04 Feb 2012 16:42:23 GMT
Until we formalize the new recommendation, I am going to stick with the
current 3 working days proposal unless we hear other objections or special
need from the community.

Monday or Friday release is as good as any other day of the week. Monday
actually gives the community a couple week-end days to react to the
proposal. Any choice would be an arbitrary choice and can be argued one way
or the other.

On Fri, Feb 3, 2012 at 7:23 PM, Pinaki Poddar <> wrote:

> Hi Albert,
> > Please post your concerns, comments or suggestions (if any) to this dev
> > mailing list.
> We should formalize that a notice for branching and code freeze on trunk
> must be at least of seven calendar days or five working days in advance. I
> have mentioned that before when Mark planned for a 2.2.0 branch.
> This is to give the community members a scope to discuss and complete their
> ongoing work.
> > We plan to copy trunk to 2.2.x branch on 2/6/2012 (Mon)
> Also a middle of the week is a better choice for a code freeze than Monday
> or Friday. Not only in this case, but in general.
> -----
> Pinaki Poddar
> Chair, Apache OpenJPA Project
> --
> View this message in context:
> Sent from the OpenJPA Developers mailing list archive at

Albert Lee.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message