You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-dev@incubator.apache.org by Xavier Hanin <xa...@gmail.com> on 2007/07/19 14:40:44 UTC
preparing Ivy 2.0.0 alpha 2 announcement
Hi,
If nobody sends a -1 vote for the 2.0 alpha 2 release of Ivy on the
general@i.a.o list until tonight, we will be able to officially release it.
Thus I would like to gather feedback about the announcement I plan to send
tomorrow:
--------------------------8<--------------------------------------------
July 20 2007 - The Ivy incubator project is please to announce its
2.0.0 alpha 2 release, a new step on the road toward 2.0 final.
Ivy is a tool for managing (recording, tracking, resolving and
reporting) project dependencies, characterized by flexibility,
configurability, and tight integration with Apache Ant.
This second release of Ivy in the Apache incubator is still an
alpha version, as such we do not guarantee any stability, API and features
are still likely to change until final 2.0.0 version. Still we encourage
the use of this version for early testing.
This version focus was to clean the code to get better readability
and improve maven 2 compatibility along with several other
bug fixes and improvement.
Download the 2.0.0 alpha 2 release files at:
http://incubator.apache.org/ivy/download.html
More information can be found on the Ivy website -
http://incubator.apache.org/ivy/
Regards,
Xavier Hanin (2.0.0-alpha-2 release mgr)
--------------------------8<--------------------------------------------
What do you think?
Xavier
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://incubator.apache.org/ivy/
http://www.xoocode.org/
Re: preparing Ivy 2.0.0 alpha 2 announcement
Posted by Steve Loughran <st...@apache.org>.
Xavier Hanin wrote:
> On 7/19/07, Steve Loughran <st...@apache.org> wrote:
do you think?
>>
>> 1. I'm actually automating my release notifications these days; one
>> advantage of a two week release cycle is it encourages you to do that. I
>> have a template txt file that gets all its ant properties expanded.
>> Things I expand include
>>
>> -version number
>> -SVN commit number and full branch
>> -sha1 checksum of all artifacts
>>
>> I still have to hand patch in the release notes from jira, but that's
>> about it.
>
>
> What do you mean by release notifications? Is it the announcement? The
> vote?
> Something else?
work releases dont need a vote. they go out every second friday, so we
just ship an announcement with a change log and the checksums. The
template that gets created is something that can be edited before the
announcement goes out, but it means that I dont need to bother with the
work of creating checksums and other bits of consistency across the file.
>
> I think announcement must be reviewed and discussed each time, to get
> something accurate. So the advantage of property expansion is not
> obvious in
> this case IMHO. For the votes, indeed mails are very similar from time to
> time, so automating them could be useful. So would the tasks documented in
> the "making a release" documentation, like changing the html templates
> titles. It doesn't take too long to do, but automating these steps would be
> nice.
>
> Regarding the text, I'd be far more enthusiastic about adoption. You
>> want people to be excited about downloading it, not scared. Certainly
>> we've been running the old release over 1.4.1-compatible files with no
>> obvious problems.
>
>
> Indeed, we want people to be excited, not scared. But on the other hand we
> haven't run much tests on this version, and we have introduced some changes
> (like the relative path handling) which are likely to cause problems in
> some
> situation. Don't get me wrong, I like your words, but I feel like a strong
> encouragement to try the version would be better suited for a beta version
> than an alpha version. Maybe we should have labeled this version beta 1?
> Anyway, maybe we could keep something slightly less strong than your
> suggestion. Maybe just removing the "strongly" before encourage would be
> ok.
sounds good to me. Like I say, I've been using the alpha-1 alongside
1.4.1; no problems so far, except I get told off for using old
configuration filenames
>
> What do you guys think ?
>
> Xavier
>
> --------
>>
>> This second release of Ivy in the Apache incubator is still an alpha
>> version, and
>> as such we do not guarantee any stability, especially of the API, until
>> the final
>> 2.0.0 version ships. In practise, the ant tasks and core functionality
>> do appear
>> to be working, to the extent that the new version can be switched in
>> over the 1.4.1 release.
>>
>>
>> Key features of the 2.0.0-alpha-2 release are
>> * enhanced support for reading, Maven2 POM files
>> * cleaner code for easier developer participation
>> * Minor bug fixes as documented in Jira.
>>
>> We strongly encourage all users of Ivy to try this new version, so that
>> any remaining compatibility
>> issues can be reported and resolved before the product is released.
>> Issues should be reported
>> to issues.apache.org/jira
>>
>> ----
>>
>>
>> --
>> Steve Loughran http://www.1060.org/blogxter/publish/5
>> Author: Ant in Action http://antbook.org/
>>
>
>
>
--
Steve Loughran http://www.1060.org/blogxter/publish/5
Author: Ant in Action http://antbook.org/
Re: preparing Ivy 2.0.0 alpha 2 announcement
Posted by Xavier Hanin <xa...@gmail.com>.
On 7/19/07, Steve Loughran <st...@apache.org> wrote:
>
> Xavier Hanin wrote:
> > Hi,
> >
> > If nobody sends a -1 vote for the 2.0 alpha 2 release of Ivy on the
> > general@i.a.o list until tonight, we will be able to officially release
> it.
> >
> > Thus I would like to gather feedback about the announcement I plan to
> send
> > tomorrow:
> > --------------------------8<--------------------------------------------
> > July 20 2007 - The Ivy incubator project is please to announce its
> > 2.0.0 alpha 2 release, a new step on the road toward 2.0 final.
> >
> > Ivy is a tool for managing (recording, tracking, resolving and
> > reporting) project dependencies, characterized by flexibility,
> > configurability, and tight integration with Apache Ant.
> >
> > This second release of Ivy in the Apache incubator is still an
> > alpha version, as such we do not guarantee any stability, API and
> features
> > are still likely to change until final 2.0.0 version. Still we encourage
> > the use of this version for early testing.
> >
> > This version focus was to clean the code to get better readability
> > and improve maven 2 compatibility along with several other
> > bug fixes and improvement.
> >
> > Download the 2.0.0 alpha 2 release files at:
> > http://incubator.apache.org/ivy/download.html
> >
> > More information can be found on the Ivy website -
> > http://incubator.apache.org/ivy/
> >
> > Regards,
> > Xavier Hanin (2.0.0-alpha-2 release mgr)
> > --------------------------8<--------------------------------------------
> >
> > What do you think?
>
> 1. I'm actually automating my release notifications these days; one
> advantage of a two week release cycle is it encourages you to do that. I
> have a template txt file that gets all its ant properties expanded.
> Things I expand include
>
> -version number
> -SVN commit number and full branch
> -sha1 checksum of all artifacts
>
> I still have to hand patch in the release notes from jira, but that's
> about it.
What do you mean by release notifications? Is it the announcement? The vote?
Something else?
I think announcement must be reviewed and discussed each time, to get
something accurate. So the advantage of property expansion is not obvious in
this case IMHO. For the votes, indeed mails are very similar from time to
time, so automating them could be useful. So would the tasks documented in
the "making a release" documentation, like changing the html templates
titles. It doesn't take too long to do, but automating these steps would be
nice.
Regarding the text, I'd be far more enthusiastic about adoption. You
> want people to be excited about downloading it, not scared. Certainly
> we've been running the old release over 1.4.1-compatible files with no
> obvious problems.
Indeed, we want people to be excited, not scared. But on the other hand we
haven't run much tests on this version, and we have introduced some changes
(like the relative path handling) which are likely to cause problems in some
situation. Don't get me wrong, I like your words, but I feel like a strong
encouragement to try the version would be better suited for a beta version
than an alpha version. Maybe we should have labeled this version beta 1?
Anyway, maybe we could keep something slightly less strong than your
suggestion. Maybe just removing the "strongly" before encourage would be ok.
What do you guys think ?
Xavier
--------
>
> This second release of Ivy in the Apache incubator is still an alpha
> version, and
> as such we do not guarantee any stability, especially of the API, until
> the final
> 2.0.0 version ships. In practise, the ant tasks and core functionality
> do appear
> to be working, to the extent that the new version can be switched in
> over the 1.4.1 release.
>
>
> Key features of the 2.0.0-alpha-2 release are
> * enhanced support for reading, Maven2 POM files
> * cleaner code for easier developer participation
> * Minor bug fixes as documented in Jira.
>
> We strongly encourage all users of Ivy to try this new version, so that
> any remaining compatibility
> issues can be reported and resolved before the product is released.
> Issues should be reported
> to issues.apache.org/jira
>
> ----
>
>
> --
> Steve Loughran http://www.1060.org/blogxter/publish/5
> Author: Ant in Action http://antbook.org/
>
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://incubator.apache.org/ivy/
http://www.xoocode.org/
Re: preparing Ivy 2.0.0 alpha 2 announcement
Posted by Steve Loughran <st...@apache.org>.
Xavier Hanin wrote:
> Hi,
>
> If nobody sends a -1 vote for the 2.0 alpha 2 release of Ivy on the
> general@i.a.o list until tonight, we will be able to officially release it.
>
> Thus I would like to gather feedback about the announcement I plan to send
> tomorrow:
> --------------------------8<--------------------------------------------
> July 20 2007 - The Ivy incubator project is please to announce its
> 2.0.0 alpha 2 release, a new step on the road toward 2.0 final.
>
> Ivy is a tool for managing (recording, tracking, resolving and
> reporting) project dependencies, characterized by flexibility,
> configurability, and tight integration with Apache Ant.
>
> This second release of Ivy in the Apache incubator is still an
> alpha version, as such we do not guarantee any stability, API and features
> are still likely to change until final 2.0.0 version. Still we encourage
> the use of this version for early testing.
>
> This version focus was to clean the code to get better readability
> and improve maven 2 compatibility along with several other
> bug fixes and improvement.
>
> Download the 2.0.0 alpha 2 release files at:
> http://incubator.apache.org/ivy/download.html
>
> More information can be found on the Ivy website -
> http://incubator.apache.org/ivy/
>
> Regards,
> Xavier Hanin (2.0.0-alpha-2 release mgr)
> --------------------------8<--------------------------------------------
>
> What do you think?
1. I'm actually automating my release notifications these days; one
advantage of a two week release cycle is it encourages you to do that. I
have a template txt file that gets all its ant properties expanded.
Things I expand include
-version number
-SVN commit number and full branch
-sha1 checksum of all artifacts
I still have to hand patch in the release notes from jira, but that's
about it.
Regarding the text, I'd be far more enthusiastic about adoption. You
want people to be excited about downloading it, not scared. Certainly
we've been running the old release over 1.4.1-compatible files with no
obvious problems.
--------
This second release of Ivy in the Apache incubator is still an alpha
version, and
as such we do not guarantee any stability, especially of the API, until
the final
2.0.0 version ships. In practise, the ant tasks and core functionality
do appear
to be working, to the extent that the new version can be switched in
over the 1.4.1 release.
Key features of the 2.0.0-alpha-2 release are
* enhanced support for reading, Maven2 POM files
* cleaner code for easier developer participation
* Minor bug fixes as documented in Jira.
We strongly encourage all users of Ivy to try this new version, so that
any remaining compatibility
issues can be reported and resolved before the product is released.
Issues should be reported
to issues.apache.org/jira
----
--
Steve Loughran http://www.1060.org/blogxter/publish/5
Author: Ant in Action http://antbook.org/
Re: preparing Ivy 2.0.0 alpha 2 announcement
Posted by Xavier Hanin <xa...@gmail.com>.
On 7/19/07, Gilles Scokart <gs...@gmail.com> wrote:
>
> Perfect.
>
> I just thing that the 'negative' part of the message should be
> shorter. For
> example :
>
> This second release of Ivy in the Apache incubator is an alpha version,
> the
> API and the features might change until final 2.0.0 version. Still we
> encourage the use of this version for early testing.
>
> What do you think?
Indeed, I like it shorter too.
Xavier
Gilles
>
>
> > -----Original Message-----
> > From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> > Sent: jeudi 19 juillet 2007 16:41
> > To: ivy-dev@incubator.apache.org
> > Subject: preparing Ivy 2.0.0 alpha 2 announcement
> >
> > Hi,
> >
> > If nobody sends a -1 vote for the 2.0 alpha 2 release of Ivy on the
> > general@i.a.o list until tonight, we will be able to officially release
> > it.
> >
> > Thus I would like to gather feedback about the announcement I plan to
> send
> > tomorrow:
> > --------------------------8<--------------------------------------------
> > July 20 2007 - The Ivy incubator project is please to announce its
> > 2.0.0 alpha 2 release, a new step on the road toward 2.0 final.
> >
> > Ivy is a tool for managing (recording, tracking, resolving and
> > reporting) project dependencies, characterized by flexibility,
> > configurability, and tight integration with Apache Ant.
> >
> > This second release of Ivy in the Apache incubator is still an
> > alpha version, as such we do not guarantee any stability, API and
> features
> > are still likely to change until final 2.0.0 version. Still we encourage
> > the use of this version for early testing.
> >
> > This version focus was to clean the code to get better readability
> > and improve maven 2 compatibility along with several other
> > bug fixes and improvement.
> >
> > Download the 2.0.0 alpha 2 release files at:
> > http://incubator.apache.org/ivy/download.html
> >
> > More information can be found on the Ivy website -
> > http://incubator.apache.org/ivy/
> >
> > Regards,
> > Xavier Hanin (2.0.0-alpha-2 release mgr)
> > --------------------------8<--------------------------------------------
> >
> > What do you think?
> >
> > Xavier
> > --
> > Xavier Hanin - Independent Java Consultant
> > http://xhab.blogspot.com/
> > http://incubator.apache.org/ivy/
> > http://www.xoocode.org/
>
>
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://incubator.apache.org/ivy/
http://www.xoocode.org/
RE: preparing Ivy 2.0.0 alpha 2 announcement
Posted by Gilles Scokart <gs...@gmail.com>.
Perfect.
I just thing that the 'negative' part of the message should be shorter. For
example :
This second release of Ivy in the Apache incubator is an alpha version, the
API and the features might change until final 2.0.0 version. Still we
encourage the use of this version for early testing.
What do you think?
Gilles
> -----Original Message-----
> From: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> Sent: jeudi 19 juillet 2007 16:41
> To: ivy-dev@incubator.apache.org
> Subject: preparing Ivy 2.0.0 alpha 2 announcement
>
> Hi,
>
> If nobody sends a -1 vote for the 2.0 alpha 2 release of Ivy on the
> general@i.a.o list until tonight, we will be able to officially release
> it.
>
> Thus I would like to gather feedback about the announcement I plan to send
> tomorrow:
> --------------------------8<--------------------------------------------
> July 20 2007 - The Ivy incubator project is please to announce its
> 2.0.0 alpha 2 release, a new step on the road toward 2.0 final.
>
> Ivy is a tool for managing (recording, tracking, resolving and
> reporting) project dependencies, characterized by flexibility,
> configurability, and tight integration with Apache Ant.
>
> This second release of Ivy in the Apache incubator is still an
> alpha version, as such we do not guarantee any stability, API and features
> are still likely to change until final 2.0.0 version. Still we encourage
> the use of this version for early testing.
>
> This version focus was to clean the code to get better readability
> and improve maven 2 compatibility along with several other
> bug fixes and improvement.
>
> Download the 2.0.0 alpha 2 release files at:
> http://incubator.apache.org/ivy/download.html
>
> More information can be found on the Ivy website -
> http://incubator.apache.org/ivy/
>
> Regards,
> Xavier Hanin (2.0.0-alpha-2 release mgr)
> --------------------------8<--------------------------------------------
>
> What do you think?
>
> Xavier
> --
> Xavier Hanin - Independent Java Consultant
> http://xhab.blogspot.com/
> http://incubator.apache.org/ivy/
> http://www.xoocode.org/