Mailing-List: contact dev-help@tiles.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tiles.apache.org
Received-SPF: pass (athena.apache.org: domain of antonio.petrelli@gmail.com
 designates 209.85.223.182 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=gk2RuinEFMqg2PIlj3IZDe/Hn5VOlPxBAEjThZMeb1j0n3ezZudZCLlC5l4nUEGsVO
         6gjClbDukP8bzqPbkWrJy2BQKDkyA9dU3YJaog7MJa280mcQvkAXxuRMH57ZcdZwnHQi
         BjvUaTgrWy3aYO2tzKg6IGUDEl/LJB2Qo7WY4=
MIME-Version: 1.0
In-Reply-To: <1272827678.12298.14.camel@localhost.localdomain>
References: <30330667.165141272045170121.JavaMail.jira@thor>
	 <1515259.61272729236161.JavaMail.jira@thor>
	 <1272803734.10088.61.camel@localhost.localdomain>
	 <y2kaae96ca1005020506ld99f86f5g85a8c896babe6d57@mail.gmail.com>
	 <1272827678.12298.14.camel@localhost.localdomain>
Date: Mon, 3 May 2010 09:26:25 +0200
Message-ID: <s2yaae96ca1005030026gdab51e6ey400998537740cace@mail.gmail.com>
Subject: Re: [jira] Commented: (TILES-506) Fix link to jira under "Project
	Information --> Issue tracking"
From: Antonio Petrelli <antonio.petrelli@gmail.com>
To: dev@tiles.apache.org
Content-Type: text/plain; charset=ISO-8859-1

2010/5/2 Mck <mick@semb.wever.org>:
>
>> First of all please close the TILES-506 issue.
>
> Done.

Ok, but you can close directly the issue, not passing the "resolved"
state. When we were on the other JIRA instance, we created a custom
workflow without the "resolved" and other states, since, in our case,
they are meaningless.
Usually, resolved means that the developer thinks he had finished his work.
Closed means that the reporter tested it and says that it works.
Usually we don't have such a feedback from the reporter, so the
"resolved" state is useless.

> But may i ask why? since i know that more commits will be necessary
> before the fix is complete. That is after tiles-master is (voted and)
> released to version 2 then the other pom files must be updated and
> commited. Only then the website will have correct links to the
> issue-tracker?

Not necessarily. If you like, you can deploy a snapshot (mvn deploy),
let the other project depend on the snapshot and deploy the website
(mvn site:deploy).

Antonio