Hi all,
I propose the following plan to release AntUnit 1.0. I also propose
to be the release manager myself.
* release AntUnit 1.0Beta1 next week after ant 1.7.0beta2 is out.
* the beta release uses the current code, maybe some adaptions need to be
made to the documentation.
* start using the beta on Ant's own code base.
* start building the example's from "the Ant book" in Gump - actually
this could happen earlier if anybody finds time to commit working
Gump descriptors
* we'll probably identify areas where AntUnit is lacking while using
it on core, so I expect a new beta build in a few weeks time.
* release 1.0 once we feel it is good to go. This may be a few weeks
after the second beta or we may need a third beta, we'll see.
Stefan
To unsubscribe, e-mail: dev-unsubscribe (AT) ant (DOT) apache.org
For additional commands, e-mail: dev-help (AT) ant (DOT) apache.org

all good, but unfortunately +0 from me (for now) - please go ahead, I
wish I could help out
To unsubscribe, e-mail: dev-unsubscribe (AT) ant (DOT) apache.org
For additional commands, e-mail: dev-help (AT) ant (DOT) apache.org

9/15/06, Stefan Bodewig <bodewig (AT) apache (DOT) orgwrote:

Hi all,

I propose the following plan to release AntUnit 1.0. I also propose
to be the release manager myself.

* release AntUnit 1.0Beta1 next week after ant 1.7.0beta2 is out.

+1

* the beta release uses the current code, maybe some adaptions need to be
made to the documentation.

* start using the beta on Ant's own code base.

for unit tests

+1 - although this is a little chicken and egg!
I assume this will be done the same way as junit? i.e. a jar file
in $trunk/lib/optional

* start building the example's from "the Ant book" in Gump - actually
this could happen earlier if anybody finds time to commit working
Gump descriptors

* we'll probably identify areas where AntUnit is lacking while using
it on core, so I expect a new beta build in a few weeks time.

* release 1.0 once we feel it is good to go. This may be a few weeks
after the second beta or we may need a third beta, we'll see.

Stefan

To unsubscribe, e-mail: dev-unsubscribe (AT) ant (DOT) apache.org
For additional commands, e-mail: dev-help (AT) ant (DOT) apache.org
--

+1

Antoine
Nachricht
Datum: Fri, 15 Sep 2006 06:10:33 +0200
Von: Stefan Bodewig <bodewig (AT) apache (DOT) org>
An: dev (AT) ant (DOT) apache.org
Betreff: [VTE] Release plan for AntUnit 1.0

Hi all,

I propose the following plan to release AntUnit 1.0. I also propose
to be the release manager myself.

* release AntUnit 1.0Beta1 next week after ant 1.7.0beta2 is out.

* the beta release uses the current code, maybe some adaptions need to be
made to the documentation.

* start using the beta on Ant's own code base.

* start building the example's from "the Ant book" in Gump - actually
this could happen earlier if anybody finds time to commit working
Gump descriptors

* we'll probably identify areas where AntUnit is lacking while using
it on core, so I expect a new beta build in a few weeks time.

* release 1.0 once we feel it is good to go. This may be a few weeks
after the second beta or we may need a third beta, we'll see.

Stefan

To unsubscribe, e-mail: dev-unsubscribe (AT) ant (DOT) apache.org
For additional commands, e-mail: dev-help (AT) ant (DOT) apache.org

Fri, 15 Sep 2006, Peter Reilly <peter.kitt.reilly (AT) gmail (DOT) comwrote:
9/15/06, Stefan Bodewig <bodewig (AT) apache (DOT) orgwrote:

>* start using the beta on Ant's own code base.

for unit tests

of course. Any other ideas?

+1 - although this is a little chicken and egg!
I assume this will be done the same way as junit? i.e. a jar file
in $trunk/lib/optional

Exactly, see the "antunit integration" thread initiated by Matt.

Stefan

To unsubscribe, e-mail: dev-unsubscribe (AT) ant (DOT) apache.org
For additional commands, e-mail: dev-help (AT) ant (DOT) apache.org

Stefan Bodewig wrote:
Hi all,

I propose the following plan to release AntUnit 1.0. I also propose
to be the release manager myself.

* release AntUnit 1.0Beta1 next week after ant 1.7.0beta2 is out.

* the beta release uses the current code, maybe some adaptions need to be
made to the documentation.

* start using the beta on Ant's own code base.

* start building the example's from "the Ant book" in Gump - actually
this could happen earlier if anybody finds time to commit working
Gump descriptors

I get the hint :)

I will see what I can do.

To unsubscribe, e-mail: dev-unsubscribe (AT) ant (DOT) apache.org
For additional commands, e-mail: dev-help (AT) ant (DOT) apache.org

Stefan Bodewig wrote:
Hi all,

I propose the following plan to release AntUnit 1.0. I also propose
to be the release manager myself.

* release AntUnit 1.0Beta1 next week after ant 1.7.0beta2 is out.

* the beta release uses the current code, maybe some adaptions need to be
made to the documentation.

* start using the beta on Ant's own code base.

* start building the example's from "the Ant book" in Gump - actually
this could happen earlier if anybody finds time to commit working
Gump descriptors

* we'll probably identify areas where AntUnit is lacking while using
it on core, so I expect a new beta build in a few weeks time.

* release 1.0 once we feel it is good to go. This may be a few weeks
after the second beta or we may need a third beta, we'll see.

Stefan

oh, +1, of course

To unsubscribe, e-mail: dev-unsubscribe (AT) ant (DOT) apache.org
For additional commands, e-mail: dev-help (AT) ant (DOT) apache.org