Re: [Erc-help] 4.0 branch, bug fixes [Was: Backend related musings.]

[disumu <di...@us...>]

Good morning all,

So, the release_4_0_branch has been brought into existence and all the
bug fixes and code cleanup since the 4.0 release (ERC_4_0_RELEASE tag
in CVS) have been applied and committed.  These changes do not include
anything having to do with the users hash tables and other new features.
Most of those new features add small enhancements which would not affect
users' current settings, though, and could be added at a later time.

Alex Schroeder <al...@em...> wrote:
> As for versions and branches...  I agree that the last major release
...
> for ourselves, even if there are no big user visible changes.  The key
> point is that we want to release new versions, but we're not in a
> hurry...  :)

There's nothing wrong with pushing forwards with new features, major
reworkings, and experiments and releasing new versions when it feels
right, but I believe a minimal use of CVS branches is important if only
to port fixes to the latest release.  Why should users have to wait
until the next big release or have to download the development version
to get access to bug fixes when with little effort on our (the
developers') part such things could be made available to them?
Especially when these fixes are being made anyways.

We don't need to be under pressure to release bug fixes, but there's
nothing stopping us from, after fixing a number of bugs, giving our
users a chance to enjoy the improvements.  I'm sure they'd appreciate
it.

--
disumu