Re: `logging-parent` website

[Volkan Yazıcı]

Right. Will indeed use the `logging-parent` repository instead.

On Tue, Sep 26, 2023 at 10:01 PM Piotr P. Karwasz 
wrote:

> Hi Volkan,
>
> On Tue, 26 Sept 2023 at 21:00, Volkan Yazıcı  wrote:
> >
> > *Summary:* I want to place the website of `logging-parent` to `
> > logging.apache.org/parent`  served
> from a to-be-created
> > `logging-parent-site` repository. Objections?
>
> Shouldn't we use an existing repository? Wouldn't `logging-site` be enough?
> If all the sites will end up in a single repo, I don't see the point
> of creating temporary repositories.
>
> Piotr
>

[VOTE][LAZY] Release Apache Logging Parent 10.1.0

[Volkan Yazıcı]

This is a lazy-vote to release the Apache Logging Parent 10.1.0.

Source repository: https://github.com/apache/logging-parent
Commit: d19ac4a1e3b324bb22b3379d48dcada50f24c65b
Distribution: https://dist.apache.org/repos/dist/dev/logging/logging-parent
Nexus: https://repository.apache.org/content/repositories/orgapachelogging-1180
Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0

Please download, test, and cast your votes on this mailing list.

[ ] +1, release the artifacts
[ ] -1, don't release, because...

This vote is open for 24 hours and will pass unless getting a
net negative vote count. All votes are welcome and we encourage
everyone to test the release, but only the Logging Services PMC
votes are officially counted.

=== Release Notes

This minor release focuses on shipping AsciiDoc-based website
generation convenience targeting the `src/site` folder. As a part of
this effort, `logging-parent` started publishing its own website[1]
and `log4j-changelog` support switched from Markdown to AsciiDoc.

[1] https://logging.staged.apache.org/logging-parent

The introduced `bnd-maven-plugin` default auto-generates both OSGi and
JPMS descriptors. Users only need to annotate packages that are to be
exported with `org.osgi.annotation.bundle.Export`, plugin will do the
rest of the magic. Hence, no need for custom `.bnd` and/or
`module-info.java` files anymore. In particular, we expect the absence
of `module-info.java` files to avoid several IDE and testing related
headaches.

 Added

* Added `asciidoc` and `constants-tmpl-adoc` profiles to
  generate AsciiDoc-based websites from `src/site`
* Added support to auto-generate changelog entries for
  `dependabot` updates
* Added `bnd-maven-plugin` defaults to auto-generate both
  OSGi and JPMS descriptors
* Started publishing the project website[1]

 Changed

* Switched the default `log4j-changelog` configuration from
  Markdown (`.release-notes.md.ftl` and `.index.md.ftl`) to
  AsciiDoc (`.release-notes.adoc.ftl` and `.index.adoc.ftl`)
* Update `actions/checkout` to version `4.1.0`
* Update `com.github.spotbugs:spotbugs-maven-plugin`
  to version `4.7.3.6`
* Update `com.google.errorprone:error_prone_core` to
  version `2.22.0`
* Update `org.osgi:osgi.annotation` to version `8.1.0`

 Removed

* Removed `project.build.outputTimestamp` override since
  it is already provided by the parent POM and its old value
  `0` was causing reproducibility issues[2] for
  `spring-boot:repackage`

[2] https://github.com/spring-projects/spring-boot/pull/37438

 Fixed

* Replaced incorrect `java.version` Maven property override
  with `maven.compiler.{source,release,target}`

Re: [VOTE] Move Chainsaw to dormant status

[Gary Gregory]

It's been 6 days, can we close this vote?

Gary

On Sat, Sep 23, 2023 at 12:31 AM Scott Deboy  wrote:
>
> Most of the ui elements can be hidden. The explicit hidden expression
> filter and real time update support are indispensable.
>
> I use it to aggregate results from multiple hosts into a single tab and
> filter in that view.
>
> Scott
>
>
>
> On Fri, Sep 22, 2023, 7:35 PM Robert Middleton 
> wrote:
>
> > I think Chainsaw /can/ be useful, but it currently is not.  If people are
> > willing to work on it a bit more, I can help out a bit.  I can see it
> > potentially being useful for the type of work that I do(embedded work) but
> > it needs a fair amount of attention in order to get to the useful level
> > IMO.
> >
> > I have spent a fair amount of time getting it into a state where it will
> > run with newer JVMs and removing the old dependencies and re-architecting
> > the backend to be more generic and allow for inputs from all types of
> > sources.  I think the basic architecture is sound at this point, but I
> > think the GUI is much too busy to make it useful.  I have been thinking
> > about how it could be re-done though, I do have some ideas that I can put
> > in a new thread.
> >
> > Latest staging site for reference:
> > https://logging.staged.apache.org/chainsaw/2.2.0/
> >
> > -Robert Middleton
> >
> > On Fri, Sep 22, 2023 at 10:30 AM Scott Deboy 
> > wrote:
> >
> > > -1
> > >
> > > While changes may be infrequent, the project is still useful and works
> > > well. I'll continue to contribute to maintenance.
> > >
> > > Scott
> > >
> > > On Thu, Sep 21, 2023, 10:00 AM Volkan Yazıcı  wrote:
> > >
> > > > As earlier discussions[1] indicate, Chainsaw has been lacking on
> > > > maintenance and no PMC member stepped up to perform necessary chores.
> > > > This is a vote to retire the Chainsaw by means of
> > > >
> > > > - Move it to the list of dormant projects[2]
> > > > - Making it clear in its README and website that the project is not
> > > > maintained anymore
> > > > - Archive its repository[3]
> > > >
> > > > Please cast your votes on this mailing list.
> > > >
> > > > [ ] +1, retire the project
> > > > [ ] -1, don't retire, because...
> > > >
> > > > This vote is open for 72 hours and will pass unless getting a net
> > > > negative vote count. All votes are welcome and we encourage everyone,
> > > > but only the Logging Services PMC votes are officially counted. At
> > > > least 3 +1 votes and more positive than negative votes are required.
> > > >
> > > > [1] https://lists.apache.org/thread/fsykp5hxr9z0c2h85snnhnj2pq553t6q
> > > > [2] https://logging.apache.org/dormant.html
> > > > [3] https://github.com/apache/chainsaw
> > > >
> > >
> >

Re: [VOTE][LAZY] Release Apache Logging Parent 10.1.0

[Piotr P. Karwasz]

Hi Volkan,

On Wed, 27 Sept 2023 at 13:34, Volkan Yazıcı  wrote:
> Please download, test, and cast your votes on this mailing list.
>
> [ ] +1, release the artifacts
> [ ] -1, don't release, because...

It is not a big problem, but the Apache ASF parent POM version 30 was
released in June and Dependabot didn't create a PR:

https://github.com/apache/maven-apache-parent/releases/tag/apache-30

This version would allow us to override the version of a standard
Maven plugin with a property.

Right now for some reason I can not recall we are overwriting some
plugin versions from the ASF  parent (reproducibility?).

Piotr

Re: [VOTE][LAZY] Release Apache Logging Parent 10.1.0

[Gary Gregory]

I think it would be nice to use the current Apache parent pom but it is not
a blocker. Up to the RM IMO.

Gary

On Wed, Sep 27, 2023, 9:34 AM Piotr P. Karwasz 
wrote:

> Hi Volkan,
>
> On Wed, 27 Sept 2023 at 13:34, Volkan Yazıcı  wrote:
> > Please download, test, and cast your votes on this mailing list.
> >
> > [ ] +1, release the artifacts
> > [ ] -1, don't release, because...
>
> It is not a big problem, but the Apache ASF parent POM version 30 was
> released in June and Dependabot didn't create a PR:
>
> https://github.com/apache/maven-apache-parent/releases/tag/apache-30
>
> This version would allow us to override the version of a standard
> Maven plugin with a property.
>
> Right now for some reason I can not recall we are overwriting some
> plugin versions from the ASF  parent (reproducibility?).
>
> Piotr
>

Re: [VOTE][LAZY] Release Apache Logging Parent 10.1.0

[Piotr P. Karwasz]

Hi all,

On Wed, 27 Sept 2023 at 13:34, Volkan Yazıcı  wrote:
> Please download, test, and cast your votes on this mailing list.
>
> [ ] +1, release the artifacts
> [ ] -1, don't release, because...

The `maven-compiler-plugin` configuration lacks the
`true` configuration, which is used in the
main repo.

This is again not a blocker, but worth mentioning since it came out in tests.

Piotr