On 07/06/07, Henning Schmiedehausen <[EMAIL PROTECTED]> wrote:
On Wed, 2007-06-06 at 19:13 +0100, sebb wrote:
> On 06/06/07, Roland Weber <[EMAIL PROTECTED]> wrote:
> > sebb wrote:
> > > s/branch/tag/g surely?
> >
> > Eh... CVS tag = SVN branch? Whatever, the things that are
>
> No, CVS tag = SV
On Wed, 2007-06-06 at 19:13 +0100, sebb wrote:
> On 06/06/07, Roland Weber <[EMAIL PROTECTED]> wrote:
> > sebb wrote:
> > > s/branch/tag/g surely?
> >
> > Eh... CVS tag = SVN branch? Whatever, the things that are
>
> No, CVS tag = SVN tag
No. SVN tag == SVN branch == shallow directory copy.
The
This is my personal model for this stuff. YMMV
trunk ---+ main development ---
|
release branch branches/JCS_1_3
|
+ --- tag tags/JCS_1_3_RC1
|
+ --- tag tags/JCS_1_3_RC2
Hi Sebastian,
> So a release can be developed in a branch or the trunk; before the
> release is finally built the current files should be copied to a
> subdirectory of tags.
>
> The tags subdirectory should not be updated once created.
The branch was the correct term. You copy trunk into a branc
On 06/06/07, Roland Weber <[EMAIL PROTECTED]> wrote:
sebb wrote:
> s/branch/tag/g surely?
Eh... CVS tag = SVN branch? Whatever, the things that are
No, CVS tag = SVN tag
not trunk and from which you can get a named historic version
(=revision?) of what used to be in trunk :-)
In SVN, ther
sebb wrote:
> s/branch/tag/g surely?
Eh... CVS tag = SVN branch? Whatever, the things that are
not trunk and from which you can get a named historic version
(=revision?) of what used to be in trunk :-)
It's called "level" in CMVC, and I just don't want to spend
my time on learning a separate voc
On 06/06/07, Roland Weber <[EMAIL PROTECTED]> wrote:
Hi Thomas,
>> If you changed the release files manually, you
>> should commit those changes to SVN and give Sebastian some time to
>> change his vote.
>
> We were voting on the artifacts on people.apache.org/~tv/jcs/, not on
> SVN. This is at
Hi Thomas,
>> If you changed the release files manually, you
>> should commit those changes to SVN and give Sebastian some time to
>> change his vote.
>
> We were voting on the artifacts on people.apache.org/~tv/jcs/, not on
> SVN. This is at least what I understood the release-then-vote-policy
>
On 6/3/07, Martin van den Bemt <[EMAIL PROTECTED]> wrote:
Agreed. though that page probably needs a bit of a reality check.. The problem
is when someone does
a -1 with reasoning, people tend to stop voting until that vote is switched to
a +1 and if that vote
is switched to a +1 and there are en
Agreed. though that page probably needs a bit of a reality check.. The problem
is when someone does
a -1 with reasoning, people tend to stop voting until that vote is switched to
a +1 and if that vote
is switched to a +1 and there are enough votes, people that stopped voting will
keep silent.
H
Martin,
Actually, that's not true. Releases cannot be vetoed by a -1. See
http://www.apache.org/foundation/voting.html
If there's a majority approval and at least 3 +1 PMC votes, than it's up to
the release manager to decide whether or not to release. He can decide to
table the vote based on
Rony is a PMC member.. However the -1 of Sebb (which is binding and blocking)
is still there (unless
I missed his +1)..
Added Rony to the jakarta-pmc authorization file (thanx for spotting this)..
Mvgr,
Martin
Thomas Vandahl wrote:
> Hi Roland,
>
> Roland Weber wrote:
>> Hi Thomas,
>>
>>> I cou
Hi Roland,
Roland Weber wrote:
> Hi Thomas,
>
>> I could not find any information about whether Rony Flatscher is a
>> member of the PMC
>
> In the committers-only SVN module is a file board/committee-info.txt
> which lists the PMCs of all Apache projects. It's (supposed to be ;-)
> the authorit
Hi Thomas,
> I could not find any information about whether Rony Flatscher is a
> member of the PMC
In the committers-only SVN module is a file board/committee-info.txt
which lists the PMCs of all Apache projects. It's (supposed to be ;-)
the authoritative source. Rony Flatscher is listed there a
14 matches
Mail list logo
