s.apache.org/thread/cv194w1fqqykrhswhmm54zy9gnnv6kgm
> Example recent vote result where two packages have been excluded due to
> bugs but where release manager decided not to accelerate the voting due to
> big number of fixes coming since RC1:
> https://lists.apache.org/thread/1kovpkx0t2pm2xrwf61ycqdynp0kdl19
>
t where two packages have been excluded due to
> bugs but where release manager decided not to accelerate the voting due to
> big number of fixes coming since RC1:
> https://lists.apache.org/thread/1kovpkx0t2pm2xrwf61ycqdynp0kdl19
> Example vote where we had 24 HR accelerated vote:
> https://list
y
> consensus, for example:
> https://lists.apache.org/thread/34onls4fw189smx5gjznkk8z80t3j6lc
>
> Am Freitag, dem 01.09.2023 um 08:52 +0200 schrieb Volkan Yazıcı:
> > Is such a thing possible? It is pretty common that many Java projects
> > have
> > multiple mo
Is such a thing possible? It is pretty common that many Java projects have
multiple modules having their own release cycles. Some of these modules are
miscellaneous "utilities" to support the rest of the code base. Common
examples I can think of are
- BOM project covering a dozen other
+1
@Christofer, thanks for taking care of this.
The improvement is undeniable.
@Gary, see the date range in the URLs.
You might need to manually perform an empty search in those ranges.
On Tue, Aug 1, 2023 at 2:16 PM Christofer Dutz
wrote:
> Starting a new thread as the last one sort of dried
*[Apologies for the cross-post in BCC. I find this development important
for all Java-based ASF projects. Hence, my push to reach a wider audience.]*
In my crusade to automate whatever [practically] possible in the release
process of a Java-based ASF project, I have cracked a new puzzler:
Abstract: Signing release artifacts using an automated release
infrastructure has been officially approved by LEGAL. This enables
projects to sign artifacts using, say, GitHub Actions.
I have been trying to overhaul the Log4j release process and make it
as frictionless as possible since last
