[Uim] Should we have a stable branch?

TOKUNAGA Hiroyuki tkng at xem.jp
Fri May 14 11:06:41 EEST 2004


On Sun, 9 May 2004 21:46:58 -0700
Ken Deeter <ktdeeter at alumni.princeton.edu> wrote:

> I think instead of doing it based on application stability, branches
> should be created for API and ABI stability. If developers feel that
> the API is not yet 'complete' then no 'stable' branch should be
> created. Once there is an API which people can say "this is good
> enough, the rest is expiremental", then a branch can be created, and
> the main trunk can start to introduce non-API/ABI compatible changes.

Surely, once stable branch is created, ABI shouldn't be broken down.
But, I don't think that branches shouldn't be created until we have a
complete API.


> With only few developers, having a stable branch just for the sake of
> having a stable branch doesn't make sense to me. It will just go
> neglected. If you can say however,"this API is complete" then the
> software shouldn't require that many changes that affect stability.

I don't think so. Benefit exists certainly that I can say 'Use stable
branch!' when I'm complained that uim is unstable ;-)


Regards,

-- 
TOKUNAGA Hiroyuki
http://kodou.net/




More information about the uim mailing list