On 1 Dec 2010, at 13:32 , Bram de Kruijff wrote: > On Wed, Dec 1, 2010 at 11:00 AM, Ivo Ladage-van Doorn > <Ivo.Ladage-vanDoorn at gxsoftware.com> wrote: >> Hi Bram, >> >> Today I discussed this with Angelo and Marcel. In the Apache Felix projects >> first a 'release proposal' is created for a certain release. Once this >> proposal is approved committers are working towards this release, still >> committing on the trunk. In fact no branches are made at all, the trunk is >> just tagged as 'release candidate 1' at the moment that all issues have been >> closed. It is certainly not the intention that during this release >> preparation code is committed to the trunk that is not intended to be >> released (i.e. PoC code), which would disturb this process. As no branches >> are created at all (for overhead reasons; merging changes back and forth >> between branch and trunk) committing PoC code is definitely not appreciated. >> We agreed that we should have the same approach for Amdatu. As we are >> working towards the 0.0.6 release, any commits not intended to be released >> with 0.0.6 should be withholded. If you need a backup, commit it to your own >> sandbox, create a branch for it, or whatever. >> BTW, I promised to create the 0.0.6 branch yesterday but due to network >> outage and still failing integration tests (AMDATU-189) I didn't do that >> yet. I first want to resolve 189 and 76 before I branch, as this reduces the >> overhead involved in branching back and forth between branch and trunk. > > Another one of those religious discussions.. not getting into it any > further as I am obvisouly out-voted and am not applying for release > manager ;) I'll create a sandbox and move the httpproxy code.
As soon as we've divided the codebase into separately releaseable modules, we are affected less by this. Your bundle could then have been a new module, that simply is not released. Greetings, Marcel
