[scribus] Announce: Scribus 1.4.0 RC6 Release
jschrewe at googlemail.com
Thu Oct 20 16:19:07 UTC 2011
On 20 October 2011 17:16, Alexandre Prokoudine <
alexandre.prokoudine at gmail.com> wrote:
> On Thu, Oct 20, 2011 at 7:02 PM, Jan Schrewe wrote:
> > I personally would opt for releases with smaller changes way more often.
> > skip all that we have a development version that we work on for two years
> > and then take another year to stabilize it and then release it and only
> > bugs. That is a nice model for huge companies who charge a lot of money
> > each release. It does not really seem to work for any open source
> *skipping most of your mail, sorry*
No worries, you caught the important part ;-)
> There is quite an effective model of developing major new features in
> a branch. For instance, Blender folks figured out they need a way to
> deal with ever-raising amount of GSoC projects, so they develop those
> in branches, then group them into digestable bits and start merging
> stuff into new versions one by one. That's what GIMP team is doing now
> too: Git branches for major features with main development happening
> in the master branch.
This kind of model seems to be the way to go nowadays. Especially since the
dvcs tools like git and mercurial are actually able to handle merges without
the usual svn pain.
That's one way. Though I would bet that git's forks and pull request and
(hopefully) github keeps you going for a long time with maybe two branches
and some tags (but then again this gives you something that is similar to
> As a matter of fact, the reason GIMP 2.8 is so late is pretty much the
> same why Scribus 1.4.0 is so late. One could learn some important
> lessons from that :)
Stuff like release early and often, KISS and distributed development models
aren't exactly new. These seem to be the lessons learned.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the scribus