Re: [egit-dev] diff across branches?

[Robin Rosenberg <robin.rosenberg@xxxxxxxxxx>]

onsdag 30 september 2009 23:54:12 skrev  Alex Blewitt:
> On 30 Sep 2009, at 21:37, Robin Rosenberg wrote:
> > onsdag 30 september 2009 22:02:58 skrev  Alex Blewitt:
> >> If not, filing a bug would be good.
> >
> > Filing a bug really won't make a differense, because it is an
> > obvious omission.
>
> I really don't think it improves the image of the project by asking
> people not to file bugs. After all, it's not present in the current

Not sure a lot of outstanding unattended issues will help either.

Bugs != feature request. The project is not mature enough yet to
have much use for feature requests in the form of bug reports. 
Non-trivial feature requests can be interesting though.

> system (whether obvious or not) and having it tracked in Bugzilla
> means that it can be assigned a milestone, people can cc themselves on
> the bug, add comments, or even turn into a parent for several other
> bugs. Furthermore, it will encourage openness of defining what is
> still yet to be implemented in J/EGit which may not be apparent to
> casual users.
>
> > Any feature request for obvious features will just add unnecessary
> > work.
>
> How does having a bug in a bug tracking system create unnecessary
> work? Particularly for a project that only has 11 open bugs? Is it
> somehow going to make the feature more difficult to implement because
> there's a bug associated with it?

Again, bugs != feature requests. If we start adding all features we have
thought of we would have many hundreds of open issues and that is much less
manageable than 11 (or 50) if you look at relevant issues in the tracker at
egit.googlecode.com. I won't delete a feature request once they have
been entered unless it is completely useless, but they don't help and anything
that does not help takes energy from other tasks.

I prefer that you discuss ideas on a mailing list first, then file a report if
you get an ack that the idea is worth tracking.

> > And, oh, patches for new features and bug fixes, including patches
> > for obvious
> > features. :)
>
> All such patches must be attached to an Eclipse bug (if they're from
> non-committers). So suggesting that somehow filing the bug in the
> first place will assist this process is mistaken.

I don't follow you now. If you want to post a patch you should definitely
open an issue for that feature/bug fix.

People with practical experience from more OSS projects may have information 
to share with regard to this subject. 

-- robin