Scott Eade wrote:
> * We need to build the release. Does someone want to volunteer to
> be the release manager? Knowledge of this process is the main
> thing that has been holding back jcs releases in the past. I
> suggest that we allow someone with the necessary knowledge perform
> this role for the proposed release, but they keep the list
> informed of the tasks that are done so that others can do this in
> the future.
Ok, if nobody else steps up, I'll do it. Should be less work than a
Torque release. My guideline always has been
http://jakarta.apache.org/commons/releases/index.html and I hope this
applies here as well.
I will be using the maven1 build as far as possible. I'm not quite sure
what the vote-after-release policy really means so I propose to cut an
RC, put it on people.apache.org somewhere, vote on it and re-brand it as
1.3.0 if everything is ok. Is that the way o go?
Bye, Thomas.
|
| 
