On 5/5/08, Jörg Schaible <[EMAIL PROTECTED]> wrote:
> Hi Rahul,
>
>
>  Rahul Akolkar wrote:
>  > This is a vote to release v10 of the commons-parent pom. This is one
>  > more step towards an established m2 release process for all of
>  > Commons.
>  >
>  > Here is a summary of changes to the pom since v9, chronologically:
>  >
>  >  * Markmail archives links have been updated
>  >  * Staging repos for RCs with final version numbers are chosen such
>  > that the stage plugin can be used
>  >  * Continuum notifier has been removed to prevent further "on
>  > error" spam
>
>
> Hmmm. Although the failing continuum notifiers are a bit annoying, they are 
> still useful to detect a problem. What about sending the notification to the 
> issues list?
>
<snip/>

(thanks for taking a look -- I've read the rest of the thread, will reply here)

Sure, thats one possibility, but lets do that through the continuum
UI, which is a more lightweight process (each pom configuration change
requires a release, releases have overhead etc).

I tried to explain in a recent thread, in short:
 * Currently all notifications are sent to dev@, which IMO isn't the best option
 * It seems the continuum UI allows us to configure notifications with
a finer granularity ("on error" messages can be treated differently
than build successes or failures from a notification PoV)
 * If you're subscribed to all Commons lists (such as dev, issues,
commits) you shouldn't notice any difference WRT success and failure
messages on a per commit or nightly basis when we're done (we can drop
the error notifications, mainly caused by CI problems so far,
configure them on a per project basis as deemed fit, or retain all of
them on issues@ -- this is TBD)

Roadmap is:
1) Release v10
2) Configure notifications via continuum UI
3) Iterate over (2) as needed (no more releases for that)

Please let us know if this addresses your question above.

-Rahul

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to