gnumed-devel
[Top][All Lists]
Advanced

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

[Gnumed-devel] Re: GNUmed & blueprints


From: Gour
Subject: [Gnumed-devel] Re: GNUmed & blueprints
Date: Sun, 07 Sep 2008 07:49:29 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux)

>>>>> "Jerzy" == Jerzy Luszawski <address@hidden> writes:

Jerzy> Maybe we shoud consider leaving LP bug tracker for end-users
Jerzy> reports, while still posting bugs found by developers to this
Jerzy> list. The rationale would be different priority: when user finds
Jerzy> a bug in production version, it should be fixed ASAP, while bugs
Jerzy> found in developers' versions can be worked upon without rush,
Jerzy> and they already have at least one developer assigned to it (the
Jerzy> one who found it :-).

I still consider that ALL bugs can go the LP bug tracker. It's much
easier to find them and track them there then within dev list.

Moreover, it's possible to tie each bug with certain release, use
tags...so it's easy to distinguish bugs from different releases from the
'dev' trunk.

However, it would be even easier when GNUmed would host a code at LP,
'cause then it's would be easy to have many branches (branch in DVCS are
cheap & easy) dealing with e.g. new feature-branches, fix-branches
etc. and bugs can be linked to different branches with the end result
that it is very easy to know for each bug for which branch/release it is
related. 


Sincerely,
Gour


-- 

Gour  | Zagreb, Croatia  | GPG key: C6E7162D
----------------------------------------------------------------

Attachment: pgpaqwa2CU34O.pgp
Description: PGP signature


reply via email to

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