On 08:35 Fri 17 Jun , Jean-Christophe PLAGNIOL-VILLARD wrote: > On 08:17 Fri 17 Jun , Øyvind Harboe wrote: > > Some questions/comments: > > > > - if we look at the current way we work with OpenOCD, we just > > commit stuff to the master branch without regards to a release. > > I would like this to continue in the same manner, which I don't > > think is in conflict with what you write. > > > > - You create a fork of OpenOCD at the openocd mirror and create > > a release branch based upon some stable point in the past(or > > tip of master branch if that's the case). Push to a fork of OpenOCD. > > Release goes ahead according to your plan. You can rewrite your > > release branch on your mirror. > > > > - Once the release is ready, I(or another maintainer) push the release > > branch to the official repository. The branch is then final is never > > rewritten. > > > > > Merge window close this sunday 17th june > > > > sp? July 17. is OK by me. > sorry my mistake > the merge windows close the 19th June > so 0.5.0-rc1 is created (tag) > 0.5.0-rc1 => 19th June > 0.5.0-rc2 => 26th June > 0.5.0-rc3 => 3rd July > 0.5.0-rc4 => 10th July > 0.5.0-rc5 => 17th July > 0.5.0-rc6 => 24th July > 0.5.0 => 31th July
if we choose the reduce tfix window to 4 weeks we will have 0.5.0-rc1 => 19th June 0.5.0-rc2 => 26th June 0.5.0-rc3 => 3rd July 0.5.0-rc4 => 10th July 0.5.0 => 17th July Best Regards, J. _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
