Hello Sebastian, I was hoping we can release today/tomorrow? Maybe we can name our current blockers? (currently there is no unresolved issues for 2.1)
Separate branch means additional build target, double commits, etc. I would release in nearest couple of days with no additional branch what do you think? On Mon, Mar 18, 2013 at 12:28 PM, seba.wag...@gmail.com < seba.wag...@gmail.com> wrote: > Hi Maxim, > > I wonder if the release does lock you from committing improvements to > trunk. For example the red5 update that you mentioned to be already > somewhere in your pipe. > > Do you think it makes sense to create a branch for the 2.1 release? > So that you can commit changes to trunk (that would not got into the 2.1 > branch anyway) > I guess any kind of fixes that will be committed to branch 2.1 might be > minor enhancements or security / bug fixes anyway. But I guess the process > will take several days. And creating a TAG in the SVN for the Vote does not > mean that trunk is available to commit new things again. Actually you would > need to wait until there is really a release approved and done. > So by optimistic estimation might be next week, pessimistic estimation > might be 2-3 weeks. > > Sebastian > > -- > Sebastian Wagner > https://twitter.com/#!/dead_lock > http://www.webbase-design.de > http://www.wagner-sebastian.com > seba.wag...@gmail.com > -- WBR Maxim aka solomax