I'd like to try a new model for releases. The following work flow should allow us all to continue using devel while releasing Leo 6.2.
*The plan* 1. When Leo 6.2 is code complete I'll create a new 6.2 branch, based on devel. Leo 6.2 b1 and 6.2 final will be based on the 6.2 branch, *not* devel. 2. *devel should never be merged into the 6.2 branch*. Instead, I'll merge 6.2 branch into devel one or more times, depending on what changes are made to the 6.2 branch. I'll update the version numbers in devel *once*, after releasing Leo 6.2 final. *Details* - All release work should be done in the 6.2 branch. - Matt and I should be the only ones working in this branch. - Any last-minute code changes should be made to the 6.2 branch, *not* devel. - I'll document Leo 6.2 in devel *before* creating the 6.2 branch. After creating the 6.2 branch, any changes to the docs should be made in the 6.2 branch. *Summary* It will be several days before I create the 6.2 branch, so there is plenty of time to tweak this plan based on your comments. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/e6a09ca8-a627-4f22-a844-39c6d3829336%40googlegroups.com.
