Re: howto make a reliable release-0.22

Hi there, Barry;

I myself have stablished schemes of the kind in several workplaces.
It is a great approach that lacks some fundamental point in our
(Scarab project's) environment: Testing effort.

Developing against trunk gives a some testing capability that branches
per feature will not. Because if I'm working in issue A, and Mick in
issue B, we'll still test (even slightly) each other work, and suffer
of potential collateral damages while we code. A branch-per-feature
will isolate this until the merging, and then, a dedicated testing
will need to be done. And we don't usually have so much time to
dedicate to testing, given we don't have Scarab as our main work.

Given the scarcest resource in Scarab project is developer-time, I
think that developing in trunk is better for us. That said, sometimes
(because of experimental or revoutionary nature of the feature) is
better to branch off development. But no need to do it routinely.

just my two cents, thanks for yours ;-)
--
Jorge Uriarte Aretxaga
http://www.gailen.es
http://www.linkedin.com/in/jorgeuriarte

On Fri, Jan 9, 2009 at 11:20 AM, Copyright Witness Network Support
<[email protected]> wrote:
>
> Hi,
>
> In my company we have used Subversion for many years now. We used to
> develop using the trunk but this causes huge issues when trying to get a
> release out due to 'development' being somewhat continuous. It also
> develops odd dependencies.
>
> One year ago we moved to trunk being sacrosant. With no dev commits. We
> have each issue in Scarab worked on a separate branch (features/<id>)
> (Ive developed a lot more advanced hooks for subversion to help support
> this).
>