Henning Schmiedehausen wrote:
Vadim,
that is not the point. The procedure in itself is flawed.
You missed it too :) Existing procedure might be flawed in somebody's opinion,
and I'm not arguing that it is ideal, but proposed procedure is even worse. It
makes any release impossible: release packages can be made available only after
the release itself is made. This makes me think that such procedure comes from
the camp not taking SCM seriously.
Since the objective of the change to the process is to verify steps done by RM,
the only viable procedure, in my view, is - (1) vote on SVN rev number (with
packages made available), (2) tagging and building a release, (3) quick vote on
resulting files. It's quick sine no actual software testing need to be
performed, just verify that zip unzips and tar untars.
Vadim
There might be
files now, but the procedure still has to be aligned to ASF wide guide
lines.
Before you wonder/think about conspiracy theories: Yes, I brought the
board (i.e. Henri) attention to this. It is necessary to change the
commons release procedures and if you think that experiences of other
PMCs (Velocity) don't count, let's try with a board opinion.
Best regards
Henning
Vadim Gritsenko schrieb:
Henri Yandell wrote:
3) Creating the actual files that are going to be released and voting
on them. There's pressure to go this way, but it's not the policy yet.
Vote has passed, so now actual files are made, and are available at
the same location [1].
Vadim
[1] http://people.apache.org/~vgritsenko/regexp/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
