[Radioactive-developers] dev list - comments from a new guy

[Pawel L. <lo...@lo...>]

Guys,

Since you've probably read my post in Design group, I will not be
repeating introductions.

I'm glad dev started with QA and I'm sorta sorry to see them being 
divided. But then "what do I know about testing" ;-)?

We, dev people, should be responsible for unit testing. I would say to
do the unit tests before the actual code (XP style) but this is not good
idea for *now*, at the beginning. Let's do something without stiff
requirements, for fun, to quickly deliver working version 0.1. We will
start introducing unit testing then.

No matter what, let's build and test our stuff before check-in against
latest code base. We will create official policy to that effect when we 
have a week of broken builds.

All other official testing belongs to QA. We should help them automate
testing though.

Now to dev stuff that has not been discussed yet:
- Seeing Java selected as the tool, how do we do builds? JDK + Ant?
- What are the 3rd party packages selected for dev, incl. versions?
Axis? What else?
- Do we have short instructions on how to setup a dev environment?
- Do we have short instructions on how checkout code?
- Do we have short instructions on how to perform a build?
- Do we have short instructions on how to perform some basic integration 
tests?
- Do we have a checkin policy? Does code submitted need to be verified
by some people before checking in?
- We will start worrying about branching when we get to some stable
release. Agreed?
- What tool do we use for dev execution tracking? Tasks from SF.net OK
for everyone?
- Seen some code posted to the list. Please add it to CVS in tests 
branch, so it can be easily built and accessed by all.

(I will repeat the IRC request here) Please make sure that if a decision
is about to be made, a post to list is made so all can see it and react.

Thanks,
Pawel