trinity-users@lists.pearsoncomputing.net

Message: previous - next
Month: October 2012

Re: [trinity-users] Trinity's release model

From: Lisi <lisi.reisz@...>
Date: Thu, 11 Oct 2012 18:28:41 +0100
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