river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz" <phil.ste...@gmail.com>
Subject Re: new site added to SVN and published
Date Wed, 03 Jan 2007 04:37:57 GMT
On 1/2/07, Geir Magnusson Jr. <geir@pobox.com> wrote:
>
> I created a simple website using my standard ant and velocity based
> framework (easy to work with...) and checked that into SVN in /site.
> I also staged it for the public webserver - should be out there at
>
>    http://incubator.apache.org/river
>
> in a few hours at most.
>
> All, please try to check it out (use https, please), and if there are
> things you want changed, lets submit patches to JIRA for now.


Sorry, I did not read that last line carefully and committed some typo fixes
directly.  I assume that was OK, since the changes were only to fix typos /
references to Harmony, etc.

Something that I would like to discuss is whether we are really going to use
STATUS as described on the guidelines page.  Some of the verbiage there
makes it look like we will be using the STATUS  file + dev list as a sort of
surrogate for JIRA.  For example,

"When a specific change to the software is proposed for discussion or voting
on the mailing list, it should be presented in the form of input to the
patch command. When sent to the mailing list, the message should contain a
Subject beginning with [PATCH] and a distinctive one-line summary
corresponding to the action item for that patch. Afterwards, the patch
summary in the STATUS file should be updated to point to the Message-ID of
that message."

I would expect to see the process here 1) discuss idea on the list 2) open
JIRA ticket 3) add patch to ticket and subsequently refer to the ticket
number in discussion.

I know that we *must* maintain a STATUS file to track incubation-related
tasks, but I don't see the value in tracking all development tasks in this
file, when we have JIRA available.  What am I missing here?

Phil

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message