11 Oct
2012
11 Oct
'12
10:08 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
11 Oct
11 Oct
10:23 a.m.
New subject: [trinity-users] Trinity's release model
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
10:28 a.m.
New subject: [trinity-users] Trinity's release model
On Thursday 11 October 2012 18:08:14 Janek S. wrote:
After upgrading to 3.5.13.1 and getting a bunch of new
bugs introduced
I ran aptitude update this morning. I had no updates. So had nothing to
upgrade.
I
started thinking it might be a good idea to release new packages
continously as changes are made to the code,
Slávek has been doing that. Hence my lack of updates/upgrades this morning.
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.
Those who want to do so, can use Slávek's patches; those who don't want to use
the patches, can have it all as one great big splodge.
Best of both worlds.
Lisi
10:55 a.m.
New subject: [trinity-users] Trinity's release model
On Thursday 11 of October 2012 19:08:14 Janek S. wrote:
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
I think that while working on 3.5.13.1, we managed to prepare a development
model that could work well. In fact, we now have three options:
1. Stable version - now 3.5.13.1
2. Forthcoming updates for stable version - my ppa
3. Development version - nightly builds
I suppose that in this model, we will continue to develop. Just the fact that
the update 3.5.13 => 3.5.13.1 was very big and after a very long time. This
can be attributed to the fact that we were at the beginning of the
introduction of this development model. Now we will try to prepare SRU
versions smaller and more often.
However, about my proposal to use branches for further development I want
write later. Let me get some rest :)
Slavek
--
11:01 a.m.
New subject: [trinity-users] Trinity's release model
On Thursday 11 October 2012 18:55:27 Slávek Banko wrote:
Let me get some rest :)
You certainly deserve it, Slávek. Thanks for all your sterling work and all
the help you and the other developers give the rest of us on the list.
Lisi
11:04 a.m.
New subject: [trinity-users] Trinity's release model
On Thursday 11 October 2012 09:28:41 Lisi wrote:
On Thursday 11 October 2012 18:08:14 Janek S. wrote:
This is true, but was not documented on the TDE web site. I read about it
Slávek's repo's on this list, subject: 'Preparing updates for 3.5.13'
I admit I was a bit nervous using this repo, I use Debian stable and the idea and
practice of installing updates continuously tweaked my poor brain. It worked out
as Lisi indicated, an uptodate system at time of release.
One issue was that the original release of 3.5.13 was to buggy (imho) for a
quality release, which made updating in this fashion seem necessary. Ubuntu style
instead of Debian style :-)
I am thoughtly testing 3.5.14 and Debian Wheezy in virtualization. I may not even
update my Squeeze workstation, it works, don't mess with it.
--
Peace,
Greg
After upgrading to 3.5.13.1 and getting a bunch
of new bugs introduced
I ran aptitude update this morning. I had no updates. So had nothing to
upgrade.
I
started thinking it might be a good idea to release new packages
continously as changes are made to the code,
Slávek has been doing that. Hence my lack of updates/upgrades this
morning.
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.
Those who want to do so, can use Slávek's patches; those who don't want to
use the patches, can have it all as one great big splodge.
Best of both worlds.
Lisi
11:50 a.m.
New subject: [trinity-users] Trinity's release model
On Thursday 11 of October 2012 20:22:07 Janek S. wrote:
Instructions are on:
https://quickbuild.pearsoncomputing.net/~slavek-banko/+archive/axis
Slavek
--
This is true,
but was not documented on the TDE web site.
Indeed, it wasn't. What should I add to my sources to use Slavek's repo?
Janek
4236
days inactive
4237
days old
8 comments
5 participants
participants (5)
-
Greg Madden -
Janek S. -
Lisi -
Slávek Banko -
Timothy Pearson