You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ctakes.apache.org by Steven Bethard <st...@Colorado.EDU> on 2012/11/14 14:28:47 UTC
trunk still frozen?
What's the status of the cTAKES trunk? Is it still frozen for the pending release?
Steve
RE: trunk still frozen?
Posted by "Masanz, James J." <Ma...@mayo.edu>.
+1 for C
Note this blog post
http://lsimons.wordpress.com/2010/02/19/using-long-lived-stable-branches/
which is recommended by
http://incubator.apache.org/guides/releasemanagement.html#best-practice
The post advocates having a single stable branch (used as the basis for all releases).
A very short version, missing details, is: commits go to trunk and are merged into the stable branch if needed to be put into the release.
Something for us to consider not just for future releases but also when naming the branch that is created (do we just call it stable as the post suggests?)
-- James
> -----Original Message-----
> From: ctakes-dev-return-860-Masanz.James=mayo.edu@incubator.apache.org
> [mailto:ctakes-dev-return-860-
> Masanz.James=mayo.edu@incubator.apache.org] On Behalf Of Wu, Stephen T.,
> Ph.D.
> Sent: Thursday, November 15, 2012 10:19 AM
> To: ctakes-dev@incubator.apache.org
> Subject: Re: trunk still frozen?
>
> +1 for C
>
> stephen
>
>
> On 11/15/12 10:12 AM, "Coarr, Matt" <mc...@mitre.org> wrote:
>
> > I vote for C. I also have some code changes that are in need of a
> > commit to make it easier to collaborate.
> >
> > Matt
> >
> >
> > On 2012-11-15 11:05 , "Steven Bethard" <st...@Colorado.EDU>
> wrote:
> >
> >> On Nov 14, 2012, at 2:28 PM, Steven Bethard
> >> <St...@Colorado.EDU>
> >> wrote:
> >>> What's the status of the cTAKES trunk? Is it still frozen for the
> >>> pending release?
> >>
> >> On Nov 14, 2012, at 7:13 PM, "Chen, Pei"
> >> <Pe...@childrens.harvard.edu>
> >> wrote:
> >>> It's been getting ready for the 3.0 release
> >>
> >> Ok, we're currently working on a paper based on the
> >> relation-extractor work, and we need to make some modifications to
> >> that code. Trading diffs over email isn't really a practical option.
> >>
> >> So should we:
> >>
> >> (a) work directly in trunk, and just let the release include our
> changes?
> >> (b) create a branch for the relation extractor, and merge it back
> >> into trunk after the release?
> >> (c) create a branch for the release?
> >>
> >> Steve
> >>
> >
Re: trunk still frozen?
Posted by Steven Bethard <st...@Colorado.EDU>.
Great. Thanks Pei!
Steve
On Nov 15, 2012, at 7:58 PM, "Chen, Pei" <Pe...@childrens.harvard.edu> wrote:
> A branches/ctakes-3.0.0-incubating branch has been created. All new 3.0 tags/RC's will be created from this branch; any new code from this branch will also be added to trunk (this shouldn't an issue since there shouldn't be too many changes to the release at this point)
>
> Feel free to continue/committing to trunk as usual.
>
>> -----Original Message-----
>> From: Wu, Stephen T., Ph.D. [mailto:Wu.Stephen@mayo.edu]
>> Sent: Thursday, November 15, 2012 11:20 AM
>> To: ctakes-dev@incubator.apache.org
>> Subject: Re: trunk still frozen?
>>
>> +1 for C
>>
>> stephen
>>
>>
>> On 11/15/12 10:12 AM, "Coarr, Matt" <mc...@mitre.org> wrote:
>>
>>> I vote for C. I also have some code changes that are in need of a
>>> commit to make it easier to collaborate.
>>>
>>> Matt
>>>
>>>
>>> On 2012-11-15 11:05 , "Steven Bethard" <st...@Colorado.EDU>
>> wrote:
>>>
>>>> On Nov 14, 2012, at 2:28 PM, Steven Bethard
>>>> <St...@Colorado.EDU>
>>>> wrote:
>>>>> What's the status of the cTAKES trunk? Is it still frozen for the
>>>>> pending release?
>>>>
>>>> On Nov 14, 2012, at 7:13 PM, "Chen, Pei"
>>>> <Pe...@childrens.harvard.edu>
>>>> wrote:
>>>>> It's been getting ready for the 3.0 release
>>>>
>>>> Ok, we're currently working on a paper based on the
>>>> relation-extractor work, and we need to make some modifications to
>>>> that code. Trading diffs over email isn't really a practical option.
>>>>
>>>> So should we:
>>>>
>>>> (a) work directly in trunk, and just let the release include our changes?
>>>> (b) create a branch for the relation extractor, and merge it back
>>>> into trunk after the release?
>>>> (c) create a branch for the release?
>>>>
>>>> Steve
>>>>
>>>
>
RE: trunk still frozen?
Posted by "Chen, Pei" <Pe...@childrens.harvard.edu>.
A branches/ctakes-3.0.0-incubating branch has been created. All new 3.0 tags/RC's will be created from this branch; any new code from this branch will also be added to trunk (this shouldn't an issue since there shouldn't be too many changes to the release at this point)
Feel free to continue/committing to trunk as usual.
> -----Original Message-----
> From: Wu, Stephen T., Ph.D. [mailto:Wu.Stephen@mayo.edu]
> Sent: Thursday, November 15, 2012 11:20 AM
> To: ctakes-dev@incubator.apache.org
> Subject: Re: trunk still frozen?
>
> +1 for C
>
> stephen
>
>
> On 11/15/12 10:12 AM, "Coarr, Matt" <mc...@mitre.org> wrote:
>
> > I vote for C. I also have some code changes that are in need of a
> > commit to make it easier to collaborate.
> >
> > Matt
> >
> >
> > On 2012-11-15 11:05 , "Steven Bethard" <st...@Colorado.EDU>
> wrote:
> >
> >> On Nov 14, 2012, at 2:28 PM, Steven Bethard
> >> <St...@Colorado.EDU>
> >> wrote:
> >>> What's the status of the cTAKES trunk? Is it still frozen for the
> >>> pending release?
> >>
> >> On Nov 14, 2012, at 7:13 PM, "Chen, Pei"
> >> <Pe...@childrens.harvard.edu>
> >> wrote:
> >>> It's been getting ready for the 3.0 release
> >>
> >> Ok, we're currently working on a paper based on the
> >> relation-extractor work, and we need to make some modifications to
> >> that code. Trading diffs over email isn't really a practical option.
> >>
> >> So should we:
> >>
> >> (a) work directly in trunk, and just let the release include our changes?
> >> (b) create a branch for the relation extractor, and merge it back
> >> into trunk after the release?
> >> (c) create a branch for the release?
> >>
> >> Steve
> >>
> >
Re: trunk still frozen?
Posted by "Wu, Stephen T., Ph.D." <Wu...@mayo.edu>.
+1 for C
stephen
On 11/15/12 10:12 AM, "Coarr, Matt" <mc...@mitre.org> wrote:
> I vote for C. I also have some code changes that are in need of a commit
> to make it easier to collaborate.
>
> Matt
>
>
> On 2012-11-15 11:05 , "Steven Bethard" <st...@Colorado.EDU> wrote:
>
>> On Nov 14, 2012, at 2:28 PM, Steven Bethard <St...@Colorado.EDU>
>> wrote:
>>> What's the status of the cTAKES trunk? Is it still frozen for the
>>> pending release?
>>
>> On Nov 14, 2012, at 7:13 PM, "Chen, Pei" <Pe...@childrens.harvard.edu>
>> wrote:
>>> It's been getting ready for the 3.0 release
>>
>> Ok, we're currently working on a paper based on the relation-extractor
>> work, and we need to make some modifications to that code. Trading diffs
>> over email isn't really a practical option.
>>
>> So should we:
>>
>> (a) work directly in trunk, and just let the release include our changes?
>> (b) create a branch for the relation extractor, and merge it back into
>> trunk after the release?
>> (c) create a branch for the release?
>>
>> Steve
>>
>
Re: trunk still frozen?
Posted by "Coarr, Matt" <mc...@mitre.org>.
I vote for C. I also have some code changes that are in need of a commit
to make it easier to collaborate.
Matt
On 2012-11-15 11:05 , "Steven Bethard" <st...@Colorado.EDU> wrote:
>On Nov 14, 2012, at 2:28 PM, Steven Bethard <St...@Colorado.EDU>
>wrote:
>> What's the status of the cTAKES trunk? Is it still frozen for the
>>pending release?
>
>On Nov 14, 2012, at 7:13 PM, "Chen, Pei" <Pe...@childrens.harvard.edu>
>wrote:
>> It's been getting ready for the 3.0 release
>
>Ok, we're currently working on a paper based on the relation-extractor
>work, and we need to make some modifications to that code. Trading diffs
>over email isn't really a practical option.
>
>So should we:
>
>(a) work directly in trunk, and just let the release include our changes?
>(b) create a branch for the relation extractor, and merge it back into
>trunk after the release?
>(c) create a branch for the release?
>
>Steve
>
Re: trunk still frozen?
Posted by Steven Bethard <st...@Colorado.EDU>.
On Nov 14, 2012, at 2:28 PM, Steven Bethard <St...@Colorado.EDU> wrote:
> What's the status of the cTAKES trunk? Is it still frozen for the pending release?
On Nov 14, 2012, at 7:13 PM, "Chen, Pei" <Pe...@childrens.harvard.edu> wrote:
> It's been getting ready for the 3.0 release
Ok, we're currently working on a paper based on the relation-extractor work, and we need to make some modifications to that code. Trading diffs over email isn't really a practical option.
So should we:
(a) work directly in trunk, and just let the release include our changes?
(b) create a branch for the relation extractor, and merge it back into trunk after the release?
(c) create a branch for the release?
Steve
RE: trunk still frozen?
Posted by "Chen, Pei" <Pe...@childrens.harvard.edu>.
It's been getting ready for the 3.0 release. IIRC, The only thing remaining is pulling in UMLS resources externally (I think it's doable to jar/zip up the resources from dictionary lookup and upload it to m2 central.) After some reading, I think this should work as a simple maven artifact (and use the unpack goal to automatically unpack the contents so it'll be transparent for developers.) If someone has a chance to try that out, it would be great, otherwise I'll look into next week once I get back into the office.
> -----Original Message-----
> From: Steven Bethard [mailto:steven.bethard@Colorado.EDU]
> Sent: Wednesday, November 14, 2012 8:29 AM
> To: ctakes-dev@incubator.apache.org
> Subject: trunk still frozen?
>
> What's the status of the cTAKES trunk? Is it still frozen for the pending
> release?
>
> Steve