flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Fisher <dave2w...@comcast.net>
Subject Re: [MENTOR] Source code layout for committers
Date Wed, 08 Aug 2012 22:29:29 GMT

On Aug 8, 2012, at 12:51 PM, Igor Costa wrote:

> Alex
> Can't control it in any layouts, developers should have common sense to
> commit only what it's apply to sdk. Mentors should watching on svn code.

The project should be watching the svn tree. This Mentor will only be looking at the next
release or other major event.

The place the project can watch svn is flex-commits@i.a.o.

> A guide like "Things to do before submit", may help .

Only "svn add" files that you create. It is as simple as that.

Pay attention to conflicts when you do an "svn up" to update your tree. If someone adds an
FB file and you both use FB then there should be a conflict between the checked in copy and
the one on your checked out copy.

If you find a file that shouldn't be there then "svn log foo.bar" to determine who is too
blame. Then communicate and svn remove.

You can get a profile of non-checked in files in the checked out source tree with "svn status".
They will all have "?". That will also note added and modified files.

A tool can be written to evaluate the output of "svn status" for compliance.

Any Committer can make the mistake and any committer should fix mistakes.

Perhaps Apache Creadur (RAT) is interested in the pattern of files that MUST NOT be in the
tree. It could be a good enhancement to RAT. This could then go into a build failed condition
in a nightly build.


> ----------------------------
> Igor Costa
> www.igorcosta.com
> www.igorcosta.org
> On Wed, Aug 8, 2012 at 5:00 AM, Bertrand Delacretaz
> <bdelacretaz@apache.org>wrote:
>> On Tue, Aug 7, 2012 at 9:55 PM, Greg Reddin <gredbug@gmail.com> wrote:
>>> On Tue, Aug 7, 2012 at 2:48 PM, Carol Frampton <cframpto@adobe.com>
>> wrote:
>>>> ..."svn status" is always your friend.
>>> Yes, but to rely on that is to rely on humans always doing the right
>>> thing, which fails often :-)...
>> An svn commit hook could also be used to make sure nothing is
>> committed to "forbidden" paths.
>> I'm not sure if ASF infrastructure provides for custom per-project
>> hooks, does anyone here know?
>> -Bertrand

View raw message