Include user mailing list for RC release?

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Include user mailing list for RC release?

Jaikiran Pai
Our recent release of Ant showed up a major issue[1] which impact Ant
users. The issue was found almost as soon as Ant was released, thanks to
the user upgrading to this newer version. I think this is an issue which
could have been caught before the release, in the RC, if more people
tested the RC on their projects. I noticed that we send the VOTE mail,
for RCs, just to the Ant dev list. I'm wondering if we should even
include our Ant user mailing list for such RC votes, just to get some
attention from a bit more wider audience who might be willing to run
their projects against the RC, so that issues like these can hopefully
be caught before we actually do a release.

[1] https://bz.apache.org/bugzilla/show_bug.cgi?id=62086

-Jaikiran



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

AW: Include user mailing list for RC release?

Jan Matèrne (jhm)
+1
We could post this info to users@ too and ask for feedback.
(Have to update the ReleaseInstructions on #14 ;)

Jan

> Our recent release of Ant showed up a major issue[1] which impact Ant
> users. The issue was found almost as soon as Ant was released, thanks
> to the user upgrading to this newer version. I think this is an issue
> which could have been caught before the release, in the RC, if more
> people tested the RC on their projects. I noticed that we send the VOTE
> mail, for RCs, just to the Ant dev list. I'm wondering if we should
> even include our Ant user mailing list for such RC votes, just to get
> some attention from a bit more wider audience who might be willing to
> run their projects against the RC, so that issues like these can
> hopefully be caught before we actually do a release.
>
> [1] https://bz.apache.org/bugzilla/show_bug.cgi?id=62086
>
> -Jaikiran
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email] For additional
> commands, e-mail: [hidden email]



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Include user mailing list for RC release?

Stefan Bodewig
In reply to this post by Jaikiran Pai
On 2018-02-10, Jaikiran Pai wrote:

> Our recent release of Ant showed up a major issue[1] which impact Ant
> users. The issue was found almost as soon as Ant was released, thanks
> to the user upgrading to this newer version. I think this is an issue
> which could have been caught before the release, in the RC, if more
> people tested the RC on their projects. I noticed that we send the
> VOTE mail, for RCs, just to the Ant dev list. I'm wondering if we
> should even include our Ant user mailing list for such RC votes, just
> to get some attention from a bit more wider audience who might be
> willing to run their projects against the RC, so that issues like
> these can hopefully be caught before we actually do a release.

We used to do so, even cut beta releases so people could test them years
ago. Back then nobody tried the betas so we stopped doing them. I'm not
saying we shouldn't include the user mailing list, let's just do
that. I'm just a bit pessimistic this would have caught the problem.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

AW: Include user mailing list for RC release?

Jan Matèrne (jhm)
> We used to do so, even cut beta releases so people could test them
> years ago. Back then nobody tried the betas so we stopped doing them.
> I'm not saying we shouldn't include the user mailing list, let's just
> do that. I'm just a bit pessimistic this would have caught the problem.

Ok, but sending the mail to users@ doesn’t require much effort, but users
get the chance to react.

Jan




---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]