Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of Nascif.AbousalhNeto@sas.com
 designates 149.173.6.152 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Status Promotion Best Practice?
Date: Fri, 14 Sep 2007 13:34:01 -0400
Message-ID: <72A37CC27F2CAB44BD13E814D2F4FE0E04A255A0@mercmbx08.na.sas.com>
In-Reply-To: <46DECDB0.6080801@kuttig.com>
Thread-Topic: Status Promotion Best Practice?
Thread-Index: Acfv00Ytq13JFdw9T/uvv0WgBhMDzQHHw2ww
From: "Nascif Abousalh-Neto" <Nascif.AbousalhNeto@sas.com>
To: <ivy-user@incubator.apache.org>

A question about using status during the development cycle, in a a
scenario where different teams are responsible for the status
"promotion".

Let's say a development team publishes an artifact with status X,
indicating a basic level of unit testing.
Then a testing team retrieves this artifact (probably using
rev=3D"latest.X"), runs a suite of integration tests, and decides to
"bless" the artifact with the next status value, say Y.

How can that process be implemented? It seems the testing team would
have to do another publish or another deliver (not sure which one),
keeping the existing version but changing the status to Y.=20

Does that makes sense? I have the feeling that this operation should be
common enough to have a shortcut, perhaps something like <ivy:promote
newstatus=3D"Y" .../>

Anybody out there doing something similar?

Thanks,
  Nascif