On 03/17/2010 05:07 AM, Konstantin Kolinko wrote:
Thank you for all your votes and feedback.
I am tallying the results below.
Perhaps you can put those that passed directly inside
status.txt (somewhere near the top I presume)
as a constant and clear reminder.
However any other location is
On 03/17/2010 05:07 AM, Konstantin Kolinko wrote:
Thank you for all your votes and feedback.
I am tallying the results below.
1. Commit-Then-Review for any documentation, including JavaDoc and code
comments.
Already decided. No need to vote.
2. Allow C-T-R for changes to svn properties:
Thank you for all your votes and feedback.
I am tallying the results below.
1. Commit-Then-Review for any documentation, including JavaDoc and code
comments.
Already decided. No need to vote.
2. Allow C-T-R for changes to svn properties:
+1: Konstantin, Tim
Mark: +1 for line endings, +0
On 3/8/2010 2:00 PM, Konstantin Kolinko wrote:
I propose to relax our RTC policy and use CTR for the types of changes
listed below:
2010/3/8 Konstantin Kolinkoknst.koli...@gmail.com:
1. We already have Commit-Then-Review for any documentation, including
JavaDoc and code comments.
Already
On 08/03/2010 17:34, Konstantin Kolinko wrote:
2. I think that we can have C-T-R for any svn metadata (svn:
properties), as those are not the code. I am +1.
+1 for line endings, +0 for the rest
3. I think that we can have C-T-R for any whitespace changes in the
code. These are generally
Konstantin Kolinko knst.koli...@gmail.com wrote in message
news:427155181003081100l7078ac60q2704f09f66040...@mail.gmail.com...
I propose to relax our RTC policy and use CTR for the types of changes
listed below:
2010/3/8 Konstantin Kolinko knst.koli...@gmail.com:
1. We already have
1. We already have Commit-Then-Review for any documentation, including
JavaDoc and code comments.
2. I think that we can have C-T-R for any svn metadata (svn:
properties), as those are not the code. I am +1.
3. I think that we can have C-T-R for any whitespace changes in the
code. These are
Your vote proposal is not very much readable.
Please make a standard single request for vote and
check boxes +1, -1 (+0, -0 are irrelevant thought, but might be added as well)
On 03/08/2010 06:34 PM, Konstantin Kolinko wrote:
1. We already have Commit-Then-Review for any documentation,
CTR for non code area in TC : +1
2010/3/8 Mladen Turk mt...@apache.org:
Your vote proposal is not very much readable.
Please make a standard single request for vote and
check boxes +1, -1 (+0, -0 are irrelevant thought, but might be added as
well)
On 03/08/2010 06:34 PM, Konstantin
I propose to relax our RTC policy and use CTR for the types of changes
listed below:
2010/3/8 Konstantin Kolinko knst.koli...@gmail.com:
1. We already have Commit-Then-Review for any documentation, including
JavaDoc and code comments.
Already decided. No need to vote.
2. I think that we can
On 03/08/2010 08:00 PM, Konstantin Kolinko wrote:
I propose to relax our RTC policy and use CTR for the types of changes
listed below:
Usually a vote has a single voting item, but all those
things you've put to vote are something many projects
already have as a policy.
Allow C-T-R for
On 08.03.2010 20:00, Konstantin Kolinko wrote:
I propose to relax our RTC policy and use CTR for the types of changes
listed below:
2. I think that we can have C-T-R for any svn metadata (svn:
properties), as those are not the code. I am +1.
Allow C-T-R for changes to svn properties:
[ ]
2010/3/8 Mladen Turk mt...@apache.org:
On 03/08/2010 08:00 PM, Konstantin Kolinko wrote:
Allow C-T-R for changes to svn properties:
[ ] +1
[ ] 0
[X] -1
-1 because it can mean anything and nothing.
Changing line endings, executable flag, mime type
all falls into svn properties for which
Overall, We'd be better off leaving everything as it is.
6.0.24 had a huge amount of changes, and also a series of rapid
regressions, and probably more to follow.
To keep the branch stable, we should work in a stable manner, RTC has
worked well for that
Filip
On 03/08/2010 10:34 AM,
On 03/08/2010 12:00 PM, Konstantin Kolinko wrote:
I propose to relax our RTC policy and use CTR for the types of changes
listed below:
2010/3/8 Konstantin Kolinkoknst.koli...@gmail.com:
1. We already have Commit-Then-Review for any documentation, including
JavaDoc and code comments.
On Mon, Mar 8, 2010 at 2:00 PM, Konstantin Kolinko
knst.koli...@gmail.com wrote:
Allow C-T-R for changes to svn properties:
[ ] +1
[ X ] 0
Allow C-T-R for any whitespace changes:
[ ] +1
[ X ] 0
Allow C-T-R for trivial fixes to English messages that are in resource files
and those that
On 03/09/2010 01:47 AM, Filip Hanik - Dev Lists wrote:
Overall, We'd be better off leaving everything as it is.
6.0.24 had a huge amount of changes, and also a series of rapid
regressions, and probably more to follow.
To keep the branch stable, we should work in a stable manner, RTC has
On 03/09/2010 01:47 AM, Filip Hanik - Dev Lists wrote:
Overall, We'd be better off leaving everything as it is.
6.0.24 had a huge amount of changes, and also a series of rapid
regressions, and probably more to follow.
To keep the branch stable, we should work in a stable manner, RTC has
worked
18 matches
Mail list logo
