Hi,
I don't think we need to delete the account.
Outside of the USA, Twitter is still very active, I use it for arts
(Twitter and Instagram are the best for that IMO), several Python devs &
projects are there, my company (EU/Spain) uses it to for sharing jobs and
news, as well as many climate res
Issues I opened marked resolved fixed: 287, 294, 295, 296, 297, 329, 330,
333, 334, 335, 340
Issue I opened that has fix available: 361
On Sun, Dec 3, 2023 at 9:10 AM Elliotte Rusty Harold
wrote:
> https://issues.apache.org/jira/projects/BCEL/issues/BCEL-337 looks
> like it's fixed and should b
No, it should NOT be removed: It is used by the build/release plugins
to know which version to check for binary compatibility when the
default Maven goal runs the BC check and when the site report is
generated.
Gary
On Sun, Dec 3, 2023 at 12:13 PM Elliotte Rusty Harold
wrote:
>
> pom.xml has thi
pom.xml has this strange variable:
6.7.0
Is that supposed to be the commons bcel version? If so, update it to
6.8.0. However, it doesn't seem to be used anywhere so perhaps just
delete the line.
On Sun, Dec 3, 2023 at 4:33 PM Gary Gregory wrote:
>
> We have fixed a few bugs and added some enha
https://issues.apache.org/jira/projects/BCEL/issues/BCEL-337 looks
like it's fixed and should be closed prior to release. Might be worth
doing a quick pass through the issue tracker to see if there's
anything else in there that needs to be closed or addressed.
On Sun, Dec 3, 2023 at 4:33 PM Gary G
The claimed security issue on apache commons appears to be broken.
Possibly they're referring to this:
https://news.apache.org/foundation/entry/apache_commons_statement_to_widespread
which did not have a CVE
On Sun, Dec 3, 2023 at 4:11 PM Piotr P. Karwasz wrote:
>
> Hi Elliotte,
>
> On Sun, 3 Dec
We have fixed a few bugs and added some enhancements since Apache
Commons BCEL 6.7.0 was released, so I would like to release Apache
Commons BCEL 6.8.0.
Apache Commons BCEL 6.8.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/bcel/6.8.0-RC1 (svn
revision 65804
Hi Elliotte,
On Sun, 3 Dec 2023 at 14:13, Elliotte Rusty Harold wrote:
>
> https://issues.apache.org/jira/projects/VALIDATOR/issues/VALIDATOR-390
> and https://issues.apache.org/jira/projects/VALIDATOR/issues/VALIDATOR-357
> are both open dependency upgrades with security implications. If
> they'
We just have no idea how public and protected API are used. Binary
compatibility is easy to understand and check. I think we should keep it
that way.
Gary
On Sun, Dec 3, 2023, 9:23 AM Elliotte Rusty Harold
wrote:
> That is annoying. Unless there are much more major breaking changes
> than FastH
That is annoying. Unless there are much more major breaking changes
than FastHashMap planned for 2.0 in the near future, my inclination
would be to kill it and jump straight to 2.0. But if you want to
release 1.8 now, +0.
On Sun, Dec 3, 2023 at 1:39 PM Gary Gregory wrote:
>
> Hello Elliotte,
>
>
Too bad it's a hassle to log in, post, and log out manually. I know
Twitter has an API but that makes the release process longer. It's
almost like we need a bot that takes anything emailed to annouce@a.o,
extracts the subject, and posts that to Twitter.
Gary
On Sat, Dec 2, 2023 at 3:54 PM sebb w
Oops, I got the process wrong: A -1 vote on a release candidate is not a veto.
Gary
On Sun, Dec 3, 2023 at 8:39 AM Gary Gregory wrote:
>
> Hello Elliotte,
>
> As Sebb's comments in VALIDATOR-390 point out, this issue can't be
> fixed in the 1.x line, so your -1 would mean that there can't ever b
Hello Elliotte,
As Sebb's comments in VALIDATOR-390 point out, this issue can't be
fixed in the 1.x line, so your -1 would mean that there can't ever be
a 1.x release again. Or am I missing something?
I am happy to switch master a 2.x line after 1.8.0 is out and break
binary compatibility at that
https://issues.apache.org/jira/projects/VALIDATOR/issues/VALIDATOR-390
and https://issues.apache.org/jira/projects/VALIDATOR/issues/VALIDATOR-357
are both open dependency upgrades with security implications. If
they've already been fixed, then please close the issues.
If they haven't been fixed, I
Given the ongoing current and declining state of Twitter (to be more
polite than I should be) I vote +1 on simply deleting the entire
account. It's no longer a useful means of communicating with Java
developers.
I wouldn't be at all surprised if Space Karen decides to disable,
deactivate, and/or r
On Sat, Dec 2, 2023 at 12:01 AM Miguel Muñoz wrote:
>
> @Elliotte Rusty Harold,
> I'd like to make two unrelated points.
> 1. I wasn't suggesting the missingFilesFirst() or missingFilesLast() methods
> as a solution to the issues raised in IO-813 LastModifiedFileComparator
> should not throw exc
16 matches
Mail list logo