openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dick <michael.d.d...@gmail.com>
Subject Re: Proposed maintenance branch policy
Date Mon, 27 Apr 2009 15:21:47 GMT
Would it be easier to read if I put a link to the table? The column for
contact release manager before committing could be filled in to make it more
obvious that the release is open.

-mike

On Sun, Apr 26, 2009 at 12:29 PM, Craig L Russell <Craig.Russell@sun.com>wrote:

> Hi Miłosz,
>
> An "open" release is a branch that is still able to be committed to.
> Releases that have shipped are not open.
>
> Regards,
>
> Craig
>
>
> On Apr 26, 2009, at 12:11 AM, Miłosz Tylenda wrote:
>
>  Hi!
>>
>> Section "Where should I put my fix?", I am not sure what it means, "open
>> release". Are these 2.0.x and 1.3.x branches currently?
>>
>> Regards,
>> Milosz
>>
>>
>>  Hi,
>>>
>>> I think it would be a good idea to formalize OpenJPA's policy with
>>> regard to maintenance branch responsibilities.
>>>
>>> The draft is published at
>>> http://cwiki.apache.org/confluence/display/openjpa/OpenJPA+Release+Management
>>>  for review/comment.
>>>
>>> Feel free to comment by either posting on the wiki or discussing on
>>> this email thread. Once we have consensus, the wiki will be considered
>>> policy.
>>>
>>> Thanks,
>>>
>>> Craig
>>>
>>> Craig L Russell
>>> Architect, Sun Java Enterprise System http://db.apache.org/jdo
>>> 408 276-5638 mailto:Craig.Russell@sun.com
>>> P.S. A good JDO? O, Gasp!
>>>
>>>
>>>
> Craig L Russell
> Architect, Sun Java Enterprise System http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
>

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