On Wed, Jan 15, 2014 at 4:52 AM, Joachim Dreimann < [email protected]> wrote:
> I lean towards calling it "trunk", because that should be recognisable for > those raising issues. 0.8dev almost suggests it is a release (candidate). afaict , the issue with trunk is that it's a "movable" state of the code base . Report some issue for trunk=0.8 , release 0.8 , and later trunk=0.9 ; then reporting against trunk means something else . Therefore by using trunk we should have a mechanism (or documented release step) to batch modify tickets (i.e. trunk => version x.y.z) . > I > think we should also encourage users to provide the revision they were at, > for example by calling the version: > > "trunk (provide rev!)" > > I do agree , this could be a custom field combined with a ticket manipulator enforcing to set that field for version=trunk [...] -- Regards, Olemis - @olemislc
