If I am resolving some particular JIRA bug or feature and I come across a
condition like Patrick pointed out...
if (someCondition)
doSomething;
doSomethingElse;
I would just fix it as part of the JIRA bug I was already resolving. No new
JIRA bug, no new paperwork, just resolve the issue.
> I'm a little more nervous about "things that are wrong" unless we
> make it clear that it's only things that have no externally visible
> behavior. These should have real bug numbers and descriptions that
> users can search.
The problem is that if I stumble across code like this:
if (some
used for
commits that don't merit a full issue of their own.
Thoughts?
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, August 18, 2006 8:50 AM
To: open-jpa-dev@incubator.apache.org
Subject: Re
ems, Inc.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 18, 2006 8:50 AM
> To: open-jpa-dev@incubator.apache.org
> Subject: Re: JIRA bug tracking of code changes
>
> I have asked the question on infrastructure@, but we
+1 for adding enforcement. At worst it's a minor inconvenience, and it's a
good habit to get into.
If there's an impact to any other projects or if it's going to be a
nightmare to implement I'll reconsider.
-Mike
On 8/18/06, Craig L Russell <[EMAIL PROTECTED]> wrote:
I have asked the question
I have asked the question on infrastructure@, but we might also find
out if the others on openjpa want to have enforcement of JIRA issue
on commits.
What do you all think?
Craig
On Aug 18, 2006, at 8:34 AM, Kevin Sutter wrote:
That did the trick, Craig. Thanks!
Now that we are on the sa
That did the trick, Craig. Thanks!
Now that we are on the same page, we're back to your original question of
whether this is enforceable or not. (And, if we even to make this
enforceable.) I would guess that we have to revert to some outside tooling
such as SCMBug to make this enforceable.
Ke
Hi Kevin,
You should be able to see svn now.
I added you to openjpa-developers (you need this anyway).
I added jira-users to permissions to see svn checkins. (Actually,
this should be the default for all svn checkins for the Apache
installation. I've made a note).
Try it now.
Craig
On A
Hi Kevin,
I'll check. JIRA uses users' profiles and capabilities, and it might
be that you don't have privileges to see the svn stuff.
Craig
On Aug 18, 2006, at 6:17 AM, Kevin Sutter wrote:
Craig,
I must be blind or something. I looked at OPENJPA-3 before and I
don't see
the "change his
Craig,
I must be blind or something. I looked at OPENJPA-3 before and I don't see
the "change history". I see the attached diff file, but that won't always
be the case with committers. I am logged into JIRA. Is there some other
configuration that I need to do to view these changes?
Thanks,
Ke
Hi Kevin,
On Aug 17, 2006, at 7:16 AM, Kevin Sutter wrote:
As a start, it would be good if we had this plugin support:
http://www.atlassian.com/software/jira/docs/v3.2/svn_integration.html
Do we know if this is available for our SVN/JIRA setup within Apache?
Having the extra tab with the corr
As a start, it would be good if we had this plugin support:
http://www.atlassian.com/software/jira/docs/v3.2/svn_integration.html
Do we know if this is available for our SVN/JIRA setup within Apache?
Having the extra tab with the corresponding file adds, deletes, and modifies
would be nice.
Kev
Hi Kevin,
SVN does have a tie-in to JIRA at Apache. The key is to include the
project-issue as the first characters of the commit message. Then
JIRA will magically (ask infrastructure) pick up the commit and
update the issue for you.
http://issues.apache.org/jira/browse/OPENJPA-3
svn com
13 matches
Mail list logo
