Marshall Schor wrote: > Eddie Epstein wrote: >> I think it is a good idea to provide a hotfix for problems deemed to be >> important enough. How will we deal with additional hotfixes? Will they >> all >> remain available? for the duration of the release or longer? When the >> next >> release is made, will there be a "final" release for the previous? I'm >> sure >> there are good answers for these, just wondering what they will be. >> > I think the idea of a hotfix is that it is for a particular release > (hence the branch from the tag), and the fix is also incorporated into > the main trunk, so the next official regular release picks up the hot fix.
+1, that also my plan. > > Re: lifecycles of releases and hot fixes - my understanding is that > these are write-once things - which remain available "forever". We keep > the often-referred to versions of things (perhaps the last year or 2's > releases) on the Apache Mirror distribution system, and things older > than that are available on the Apache archive site "forever". > > -Marshall >> Eddie >> >> On Mon, Jun 23, 2008 at 1:09 PM, Michael Baessler >> <[EMAIL PROTECTED]> >> wrote: >> >> >>> After we release UIMA 2.2.2 we detected two memory issues in UIMA core >>> (UIMA-1067, UIMA-1068). >>> - Remove char heap/ref heap in StringHeap of the CAS >>> - Use of the JCas cache should be configurable >>> >>> There is a project that needs a fix for these two issues so I plan to >>> provide a hotfix that just >>> fixes these two issues based on UIMA 2.2.2. The release artifact I >>> want to >>> ship is just the >>> uima-core.jar file. >>> >>> To create the hotfix will will branch on UIMA 2.2.2 and applied the >>> fixes >>> for the two issues. >>> >>> -- Michael >>> >>> >>> >> >> >
