To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-configuration-test has an issue affecting its community
integrati
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-email has an issue affecting its community integration.
This issue
Henri Yandell wrote:
The most important part to consider is 'What can go wrong?'.
In the case of making 1.0 and deleting if it fails, let's imagine the
release then pauses. For example Collections 3.3. We would then have
the possibility of a 3.3 tag that people would think meant something.
In t
On Sun, Jun 28, 2009 at 5:24 AM, Henri Yandell wrote:
> The most important part to consider is 'What can go wrong?'.
Ok, here's my reply to your question. Assuming that I am forced to
follow the procedure as outlined by you. That means that I am forced
not to use the maven-release-plugin. Consequ
On 28/06/2009, Jochen Wiedmann wrote:
> On Sun, Jun 28, 2009 at 5:24 AM, Henri Yandell wrote:
>
> > The most important part to consider is 'What can go wrong?'.
>
>
> Ok, here's my reply to your question. Assuming that I am forced to
> follow the procedure as outlined by you. That means that I a
On Mon, Jun 29, 2009 at 12:13 AM, sebb wrote:
> Are you sure that is the case?
>
> The Commons release wiki page implies that one can provide the RC number as in
>
> RC2
Obviously commons has managed to introduce yet another peculiarity in
its release process ... I have to admit that I don't k
