[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [dali-dev] first commits...
|
Max,
Up to this point we have been taking the following approach- All new
features are logged in bugzilla and assigned. When a feature has been
completed, the ER is closed in bugzilla. This is one way of
communicating status to the community. For bugs, when not being fixed
in the course of new development, bugs are logged in bugzilla, and the
commit comment contains the associated bug number. We have not had a
strict policy that every commit have a bug #, but as we transition to
JST, these rules will become more formal.
To specifically address your question, I would like you to log any bugs
that you come across. After having entered them, if you were going to
fix the issue, you could then assign the bug to yourself and continue
on. At this point, for truly minor issues, feel free to make trivial
changes without entering a bug. As noted above, this process may not
last much longer, but for now is fine.
We don't have a commit notification mailing list set up for Dali at this
time. I imagine one could be created should this become necessary, but
I don't know that it would.
Also, not sure which bugzilla system you are looking at but the one I
see has at least 20 entries for the Dali component. :) I think your
query might be off.
Neil
Max Rydahl Andersen wrote:
...and does anyone know if there is cvs commit notification mailing
list for dali commits ?
Thanks,
max
Hi guys/gals,
I just committed a very basic fix into the dali project (mainly to
verify that my passwords/ssh still worked).
But just wondering if we should create bugs and get assigned to them
before i go fix stuff or is it just ok for
me to fix little things without syncing via the bug system (which
btw. only contain the entries i just created..)
