bdelacretaz commented on PR #533:
URL:
https://github.com/apache/incubator-baremaps/pull/533#issuecomment-1313271107
> According to the [.asf.yaml
documentation](https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-GitHubPages),
it looks like we c
bchapuis commented on PR #533:
URL:
https://github.com/apache/incubator-baremaps/pull/533#issuecomment-1313284673
Yes, I noticed this as well. I will probably give it a try and fill a ticket
if it doesn't work.
--
This is an automated message from the Apache Git Service.
To respond to th
CalvinKirs commented on issue #492:
URL:
https://github.com/apache/incubator-baremaps/issues/492#issuecomment-1313537830
> @CalvinKirs @julianhyde @LeonardBesseau I'm progressing on the various
tasks associated with the first release, and would like to have your opinion on
PGP signatures.
CalvinKirs commented on issue #492:
URL:
https://github.com/apache/incubator-baremaps/issues/492#issuecomment-1313543946
This is all the process of general release:
https://skywalking.apache.org/docs/main/v9.2.0/en/guides/how-to-release/
--
This is an automated message from the Apache
bchapuis commented on issue #492:
URL:
https://github.com/apache/incubator-baremaps/issues/492#issuecomment-1313555352
Thank you for the pointers.
I'd love the source and binary releases to be generated by the CI to prevent
issues such as differences in newline encoding. A possibilit
bchapuis merged PR #533:
URL: https://github.com/apache/incubator-baremaps/pull/533
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@bare
Hi Everyone,
The current policy is to have at least one review before merging. Some changes
need to be reviewed. However, I believe that many incremental changes (config,
cleaning, typos, etc.) can be reviewed after being merged. I'd like committers
to feel empowered to modify and improve the c
Hi Bertil,
I know that I am not reviewing much these days so my voice probably doesn't
count much as I am a bit of a bottleneck potentially, but I am in principle
against a no review policy, even for trivial stuff.
The main reason being that there should be always at least 2 people aware
of some c
