11 Oct
2012
11 Oct
'12
10:23 a.m.
After upgrading to 3.5.13.1 and getting a bunch of new
bugs introduced I
started thinking it might
be a good idea to release new packages continously as changes are made to
the code, instead of
doing a big release once every few months. I realize there are some major
changes going on in the
code and they cannot be released partially. Still I think that thanks to
git's branching and
merging capabilities it should be possible to merge some smaller changes
and bugfixes into master
and release them as update. Woludn't that be an easier way to track new
bugs introduced to the
code? Instead of getting a whole load of bug reports after a major
release, bugs would be
reported as they appear and would be easier to track down to conrete
packages and changes made in
the code.
Janek
To a certain extent this is what our SRUs are attempting to do. I do
realize that our earlier model of releasing a new version every 1-1.5
years is a bit unrealistic for most users, and hope that Slavek and
similarly minded developers continue to cherry pick commits from GIT HEAD
to produce additional SRUs in the future.
Regarding continually releasing packages, development is usually riddled
with ABI/API breakage (as is quite normal for a project of this size!),
and we simply don't have the funding to constantly rebuild and re-upload
the entire TDE system.
Tim