Thanks! We use several Confluence spaces (site, project mgmt, samples,
docs, ....) and links to pull it all together....
BTW - If you let me know which pages you're interested in, I can send
you the wiki markup off-line.....
-Donald
Michael Dick wrote:
> 2009/4/27 Michael Dick
>
>> I think this is the page [1], [2] (wiki, normal).
>>
>> Combining that page with the new one, or linking them better (maybe a new
>> category on the right is in order) is probably also needed. I think Geronimo
>> [3] has done a good job with their site - wish I could see the wiki syntax
>> to see how they did it ;-).
>
>
> I should have elaborated here.. I think that we might want to reorganize the
> overall openjpa site. The two sets of release instructions need to be
> cleaned up, and I'm sure there are other areas that can be made more
> visible.
>
> Geronimo's site seems well organized and the project management page has
> similar information to what we're adding now.
>
> -mike
>
>
>> [1] http://cwiki.apache.org/confluence/pages/viewpage.action?pageId=55076
>> [2] http://openjpa.apache.org/openjpareleasepolicy.html
>> [3] http://geronimo.apache.org/
>>
>> -mike
>>
>>
>> On Mon, Apr 27, 2009 at 12:01 PM, Craig L Russell wrote:
>>
>>> Hi Michael,
>>>
>>> I think there is a bigger piece missing. I remember we had a discussion on
>>> the branch/tag/release strategy and I can't find it now (perhaps it's an
>>> orphaned wiki page).
>>>
>>> What would make it easier to understand is to have a brief introduction to
>>> the release and maintenance strategy. If no one can find it, I'll create it
>>> from memory and put it into the wiki.
>>>
>>> Something like this: OpenJPA releases are numbered with major.minor.update
>>> schemes. Releases have a maintenance branch numbered major.minor.x. Each
>>> maintenance branch can build the next release in the series, e.g. 1.0.x will
>>> build 1.0.4-SNAPSHOT.
>>>
>>> Craig
>>>
>>>
>>> On Apr 27, 2009, at 8:21 AM, Michael Dick wrote:
>>>
>>> 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 >>>> 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!
>>>>>
>>>>>
>>>>>
>>> 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!
>>>
>>>
>