Re: is trunk stable compared to release 0.21 ?

Andrey Larionov wrote:

>On Wed, Mar 26, 2008 at 5:57 PM, Hussayn Dabbous
><[email protected]> wrote:
>> Hi;
>>
>>  I know, trunk is always considered a risk...
>>  But is it worth a try to use it as a replacement
>>  for 0.21 ? I ask, because i want to start new
>>  functionality now, but i prefer to start right
>>  from trunk, instead of our 0.21 release, so that
>>  Scarab can profit as a whole from  my next 2 months
>>  work...
>>
>>  Do i have to be prepared for any known and severe problems ?
>>  (I can live with the normal risk of getting unexpected behaviour
>>  from untested development version...)
>>
>>  Any input for decision making is welcome.
>>

>Trunk is stable only if we exclude locale bundles with errors
>(reported on our maven instance). Also LDAPSecurity have some
>unpredictable behaviour
...

>We use scarab trunk for more then 7 month. No crashes or critical
>errors occurred (we don't use report functionality)
>
>Maybe your should copy trunk to branch, and work on it?

The trunk is definitely stable enough for starting a new feature on top of it.
In my opinion it is even stable enough to deploy it on the Selfhost.
In fact it won't get any more stable than it is now, without exposing it to a wider audience.

So as I said in an earlier mail: because the current trunk already contains about a year of enhancements and fixes compared to b21, I would like to deploy it on the selfhost soon and release some weeks later, if it has proven to be stable.

On one hand we have the stable trunk which could be the basis of a release, on the other hand we have two ongoing enhancements (Andreys and Johannes) and a couple of planed enhancements (yours) which may well introduce new instability.

That's why I would suggest to create a release branch for b22 and keep the trunk open for any enhancements.

You can still create your own branch, as Andrey suggested.

Ronny


Ps. Good to see that the development of scarab is gaining some momentum