[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gzz] Fundamental change in our operations
From: |
Tuomas Lukka |
Subject: |
[Gzz] Fundamental change in our operations |
Date: |
Sat, 16 Aug 2003 12:33:49 +0300 |
User-agent: |
Mutt/1.5.4i |
It appears that we've finally reached the point I've
been looking forwards to for 4 long years.
We have a system we can start using.
I've started testing FenPDF with literature related
to our project, in fenfire CVS, module spaces.
The corresponding PDF files are in io and himalia,
~lukka/pool or ~tjl/pool - they cannot be distributed
to anyone outside the project.
This means that our working methods need some adjustments.
Up until now it's mostly been about finishing module
after module - now we'll start the exciting part: chasing
bugs.
So, I'd like to ask all participants for their ideas:
how should we change our processes?
Some questions to start off
- Should we install bugzilla or some other software,
or should we use the savannah bug system?
- How can we ensure stability of the working versions
in CVS?
Now that FenPDF and MM both work, it's vital that no-one
will break them.
We may need
1) more tests to make sure things also run -
there are no good tests for the surface layer
of fenpdf
2) to use branches more often for experimental stuff
3) to review each others' code
Also, if a change by anyone breaks FenPDF or MM, and
no other solution can be found easily (and the person
is not reachable), anyone is allowed to revert changes
(only the minimal amount, back to when things work).
Comments, discussion please!
Tuomas
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Gzz] Fundamental change in our operations,
Tuomas Lukka <=