[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [ESPResSo-devel] Bug tracker [Was: Re: Build still fails without Len

From: Olaf Lenz
Subject: Re: [ESPResSo-devel] Bug tracker [Was: Re: Build still fails without Lennard-Jones]
Date: Mon, 23 Jun 2014 10:40:39 +0200

I disagree. The main advantage of the bug tracker is that you can query bugs even when they are already gone, so that you know whether a bug is in the current version, or not. If we would include all bugs of the current development code, this archive would be really clobbered with probably very simple and temporary stuff ("You forgot to commit that file..."). Furthermore, people would not use the bug tracker for many things as it is significantly more overhead to enter something to the bug tracker than writing a quick email.

I vote to use the bug tracker for the release code and the mailing list for bugs in the development code. Alternatively, we could think to start using the github bug tracker. That is much more convenient and may be an alternative.


2014-06-13 14:50 GMT+02:00 Rudolf Weeber <address@hidden>:
On Thu, Jun 12, 2014 at 05:07:02PM +0200, Florian Weik wrote:
> I did not file a bug because the website says the bug tracker is only
> intended for release versions of espresso, is this really what we want? I'm
> quite sure that even for development versions this would overflow...
I think, bugs in the Master development branch should be included in the bug tracker, and the website should be changed.
Quite a few people, I think, use the development code for production runs.

Regards, Rudolf

Dr. rer. nat. Olaf Lenz
Institut für Computerphysik, Allmandring 3, D-70569 Stuttgart
Phone: +49-711-685-63607

reply via email to

[Prev in Thread] Current Thread [Next in Thread]