Looks like you can forward the announcement to [email protected] and Sally
will handle it. If you send the email to [email protected] from your
apache email, it'll get posted on apache.org as well. We never did this for
Log4j 2.0 from what I recall, and log4j-api isn't as prevalent as it could
be.

On 22 June 2018 at 10:43, Ralph Goers <[email protected]> wrote:

> I have no idea how to do a press release. Remko has done blog posts of all
> the recent log4j releases.
>
> Ralph
>
> > On Jun 22, 2018, at 8:41 AM, Matt Sicker <[email protected]> wrote:
> >
> > Being a 1.0 release, I think this should also be posted to announce@ as
> > well as maybe a press release? :)
> >
> > On 22 June 2018 at 10:39, Ralph Goers <[email protected]>
> wrote:
> >
> >> The Apache Log4j  team is pleased to announce the Apache Log4j Audit
> 1.0.0
> >> release!
> >>
> >> Apache Log4j Audit provides a framework for defining audit events and
> then
> >> logging them using Log4j. The framework focuses on defining the events
> and
> >> providing an easy mechanism for applications to log them, allowing
> products
> >> to provide consistency and validity to the events that are logged. It
> does
> >> not focus on how the log events are written to a data store. Log4j
> itself
> >> provides many options for that.
> >> Log4j Audit builds upon Log4j by defining its own AuditMessage. An
> >> AuditMessage is a container for structured data messages which allows a
> log
> >> message to be generated that contains a set of keys and values. The
> >> AuditMessage passes through Log4j as any other log event would.
> >>
> >>
> >> For complete information on Apache Log4j 2, including instructions on
> how
> >> to submit bug reports, patches, or suggestions for improvement, see the
> >> Apache Apache Log4j 2 website:
> >>
> >> http://logging.apache.org/log4j-audit/latest/
> >>
> >
> >
> >
> > --
> > Matt Sicker <[email protected]>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>


-- 
Matt Sicker <[email protected]>

Reply via email to