Hi Hyunsik,

Great work!

RE: patch naming what do you think about this?

Normally I name patches:

<JIRA issue ID #>.<last name>.<yyMMdd>.<n>.patch.txt

Example for OODT

OODT-578.Mattmann.032803.patch.txt

This:

1. helps identifier the contributor in the actual patch file by their last
name
(alternative, first letter of first name, and last name or some other
alternative
may be used).

2. indicates the date on which the patch was submitted in the file name

3. allows for multiple revisions (n parameter) if multiple patches in the
same day

4. Adds a .txt at the end, b/c some browsers, and HTTPD servers, don't
understand
that the .patch file extension is actually a text file and thus downloads
instead of
displaying the file in JIRA.

Thoughts about using the above scheme? I realize you guys will be doing a
bulk
of the work, compared to me, so it's really your choice, but just wanted
to share
the above since I use it in all my projects, and encourage others to as
well and
it's seemed to work out.

Cheers,
Chris

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: [email protected]
WWW:  http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++






-----Original Message-----
From: Hyunsik Choi <[email protected]>
Reply-To: "[email protected]" <[email protected]>
Date: Saturday, March 30, 2013 9:09 AM
To: tajo-dev <[email protected]>
Subject: Please review HowToContribute doc

>Hi folks,
>
>http://wiki.apache.org/tajo/HowToContribute
>
>I've written the first draft of HowToContribute page. I brought the base
>layout and some general descriptions from Hadoop's one (
>http://wiki.apache.org/hadoop/HowToContribute) because Hadoop's one
>already
>contains great and general descriptions. However, I kept only minimum,
>essential, and general guides. If this approach can cause extra noise,
>please inform me.
>
>Could anyone please review this? Feel free to give any suggestion and
>feedback on it.  Also, you can edit the wiki page.
>
>Thanks,
>Hyunsik

Reply via email to