[ALL] Change to GitHub Workflow message subjects

[sebb <se...@gmail.com>]

I discovered recently that GMail conversation mode ignores certain
subject prefixes when deciding which emails are in the same thread.

In particular, it ignores text in [brackets]; as these were used to
enclose the repo name, this resulted in merging emails from different
components.

The email subjects have been adjusted to use (parentheses) instead of
[brackets] so GMail should no longer merge mails from different
components.

Sebb

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [ALL] Change to GitHub Workflow message subjects

[sebb <se...@gmail.com>]

On Thu, 5 Oct 2023 at 17:48, Mike Drob <md...@mdrob.com> wrote:
>
> But often [VOTE] and [RESULT] are send with the same otherwise subject (and
> sometimes even [DISCUSS] before the vote, on other projects)

However in that case the merged conversations will at least relate to
the same component.
I have not personally found a problem with GMail behaviour for such messages.

Whereas with the Workflow messages, it was very easy to miss a message
about a component because it was buried in another conversation
relating to a different component.

But if there is agreement to change the convention (and the docs), I
won't object.

Sebb
> On Thu, Oct 5, 2023 at 11:43 AM sebb <se...@gmail.com> wrote:
>
> > On Thu, 5 Oct 2023 at 17:25, Gary Gregory <ga...@gmail.com> wrote:
> > >
> > > Should we use (VOTE) instead of [VOTE]?
> >
> > I doubt that is necessary.
> >
> > The GMail behaviour particularly affects the Workflow messages because
> > the same workflow names are re-used, so often the only differentiator
> > was the [component_repo]
> > e.g.
> > [GitHub] [commons-pool]: Workflow run "Java CI" is working again!
> > [GitHub] [commons-lang]: Workflow run "Java CI" is working again!
> >
> > Vote subjects include the component name in plain text.
> >
> > > Gary
> > >
> > >
> > > On Thu, Oct 5, 2023, 10:53 AM sebb <se...@gmail.com> wrote:
> > >
> > > > I discovered recently that GMail conversation mode ignores certain
> > > > subject prefixes when deciding which emails are in the same thread.
> > > >
> > > > In particular, it ignores text in [brackets]; as these were used to
> > > > enclose the repo name, this resulted in merging emails from different
> > > > components.
> > > >
> > > > The email subjects have been adjusted to use (parentheses) instead of
> > > > [brackets] so GMail should no longer merge mails from different
> > > > components.
> > > >
> > > > Sebb
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > > > For additional commands, e-mail: dev-help@commons.apache.org
> > > >
> > > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [ALL] Change to GitHub Workflow message subjects

[Mike Drob <md...@mdrob.com>]

But often [VOTE] and [RESULT] are send with the same otherwise subject (and
sometimes even [DISCUSS] before the vote, on other projects)

On Thu, Oct 5, 2023 at 11:43 AM sebb <se...@gmail.com> wrote:

> On Thu, 5 Oct 2023 at 17:25, Gary Gregory <ga...@gmail.com> wrote:
> >
> > Should we use (VOTE) instead of [VOTE]?
>
> I doubt that is necessary.
>
> The GMail behaviour particularly affects the Workflow messages because
> the same workflow names are re-used, so often the only differentiator
> was the [component_repo]
> e.g.
> [GitHub] [commons-pool]: Workflow run "Java CI" is working again!
> [GitHub] [commons-lang]: Workflow run "Java CI" is working again!
>
> Vote subjects include the component name in plain text.
>
> > Gary
> >
> >
> > On Thu, Oct 5, 2023, 10:53 AM sebb <se...@gmail.com> wrote:
> >
> > > I discovered recently that GMail conversation mode ignores certain
> > > subject prefixes when deciding which emails are in the same thread.
> > >
> > > In particular, it ignores text in [brackets]; as these were used to
> > > enclose the repo name, this resulted in merging emails from different
> > > components.
> > >
> > > The email subjects have been adjusted to use (parentheses) instead of
> > > [brackets] so GMail should no longer merge mails from different
> > > components.
> > >
> > > Sebb
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > > For additional commands, e-mail: dev-help@commons.apache.org
> > >
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

Re: [ALL] Change to GitHub Workflow message subjects

[sebb <se...@gmail.com>]

On Thu, 5 Oct 2023 at 17:25, Gary Gregory <ga...@gmail.com> wrote:
>
> Should we use (VOTE) instead of [VOTE]?

I doubt that is necessary.

The GMail behaviour particularly affects the Workflow messages because
the same workflow names are re-used, so often the only differentiator
was the [component_repo]
e.g.
[GitHub] [commons-pool]: Workflow run "Java CI" is working again!
[GitHub] [commons-lang]: Workflow run "Java CI" is working again!

Vote subjects include the component name in plain text.

> Gary
>
>
> On Thu, Oct 5, 2023, 10:53 AM sebb <se...@gmail.com> wrote:
>
> > I discovered recently that GMail conversation mode ignores certain
> > subject prefixes when deciding which emails are in the same thread.
> >
> > In particular, it ignores text in [brackets]; as these were used to
> > enclose the repo name, this resulted in merging emails from different
> > components.
> >
> > The email subjects have been adjusted to use (parentheses) instead of
> > [brackets] so GMail should no longer merge mails from different
> > components.
> >
> > Sebb
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [ALL] Change to GitHub Workflow message subjects

[Gary Gregory <ga...@gmail.com>]

Should we use (VOTE) instead of [VOTE]?

Gary


On Thu, Oct 5, 2023, 10:53 AM sebb <se...@gmail.com> wrote:

> I discovered recently that GMail conversation mode ignores certain
> subject prefixes when deciding which emails are in the same thread.
>
> In particular, it ignores text in [brackets]; as these were used to
> enclose the repo name, this resulted in merging emails from different
> components.
>
> The email subjects have been adjusted to use (parentheses) instead of
> [brackets] so GMail should no longer merge mails from different
> components.
>
> Sebb
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>