Hi Jason, Thank you for your clarification. Since 1.2 beta is out, I was under the impression that we will be stabilizing the 1.2 branch and not put any new functions/improvements. New functions/improvements can still go into 1.x. My confusion was whether to hold back commits to branches\1.2 unless it is a bug fix. As for the bug fixes, they will go into all relevant branches.
--vamsi On 12/28/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
Um... its where code for the 1.2* line of Geronimo goes. I'd imagine that if a a fix for "1.x" is applicable for the 1.2 line then it could be committed there, probably also to branches/1.1 too if its a bug fix for both. Sure improvement fixes can still go into 1.2, and be marked for fix in 1.2, since 1.2 is not yet out the door. Once 1.2 is officially out, then bugs/whatever for the 1.2 line will go into branches/1.2 and should be marked for fix in "1.2.1", etc. This seems kinda obvious to me... maybe I'm missing something in your question? --jason On Dec 27, 2006, at 8:24 PM, Vamsavardhana Reddy wrote: > What is the purpose of branches\1.2 as it stands now? Can fixes > targeted for "1.x" be committed to this branch? If not, where > should this ffixes go? Can fixes for JIRAs marked as "Improvement" > be still committed to branches\1.2 and designated as fixed in "1.2"? > > --vamsi
