Re: file-roller branched
- From: Alexander Larsson <alexl redhat com>
- To: Elijah Newren <newren gmail com>
- Cc: GNOME I18N List <gnome-i18n gnome org>, "Scott J. Harmon" <harmon ksu edu>, GNOME Documentation <gnome-doc-list gnome org>, Desktop Devel <desktop-devel-list gnome org>
- Subject: Re: file-roller branched
- Date: Wed, 21 Jun 2006 09:43:43 +0200
On Tue, 2006-06-20 at 10:53 -0600, Elijah Newren wrote:
> On 6/20/06, Scott J. Harmon <harmon ksu edu> wrote:
> > Paolo Bacchilega wrote:
> > > Hi,
> > >
> > > the file-roller module has now a gnome-2-14 branch for version 2.14,
> > > HEAD will be used to develop version 2.16
> > >
> > > Plans for 2.16 are: browse bugzilla and fix bugs.
> > >
> > Bug fixing can be done without branching unless these are architecture
> > changing bugs...
> Not quite -- bug fixing also can't be done on the branch if they are
> bugs which would require modifying translatable strings or the UI or
> would need some new feature to fix... (unless, of course, you get
> freeze break approval) ;-)
I'm slightly annoyed at this listing of rules for when you need to
branch. There is also the fact that 2.14 is *stable* and fixing bugs can
destabilize it as much as adding features can. If you're unsure of the
stability of bugfixes its very nice to be able to commit them to a
branch immediately and then move the important and stable fixes to the
Alexander Larsson Red Hat, Inc
alexl redhat com alla lysator liu se
He's a benighted zombie photographer who hides his scarred face behind a mask.
She's a wealthy cigar-chomping fairy princess on her way to prison for a
murder she didn't commit. They fight crime!
] [Thread Prev