I can't say it's a convention, it's just the pattern I've been following.
Gary
On Wed, Jun 22, 2022, 14:59 Matt Juntunen wrote:
> Gary,
>
> I was unaware of this. Is this a new convention that we've decided on?
> If not, I'd prefer to wait for the next release since "2.8" is
> consistent with
Hello.
Le mer. 22 juin 2022 à 20:59, Matt Juntunen
a écrit :
>
> Gary,
>
> I was unaware of this. Is this a new convention that we've decided on?
Although Gary's suggestion would be a slight improvement, most
of the components indeed do not follow that convention.
This is the kind of common
Gary,
I was unaware of this. Is this a new convention that we've decided on?
If not, I'd prefer to wait for the next release since "2.8" is
consistent with previous commons-configuration releases and the vote
has already started on rc2.
Regards,
Matt J
On Wed, Jun 22, 2022 at 7:45 AM Gary
Please use 2.8.0, I've been using the 3 part version format for all recent
releases. I think it would be nice to follow this naming here.
Gary
On Tue, Jun 21, 2022, 22:30 Matt Juntunen wrote:
> Thanks, Bruno! I'm going to go ahead and cancel this vote so I can fix
> the README. I also noticed
Thanks, Bruno! I'm going to go ahead and cancel this vote so I can fix
the README. I also noticed some inconsistency in the naming of the
version. In some places I called it 2.8.0 and in others 2.8. I'm going
to standardize on the shorter "2.8". RC2 should be out soon.
Regards,
Matt J
On Tue,
Hi Matt,
Inspected NOTICE, LICENSE, RELEASE-NOTES, and found no issues. Checked out
the tag, and `mvn clean test install site` passed with no errors.
The README is still showing 2.7 in the download instructions. I **think**
one of the preparation steps uses a release-plugin goal that
We have fixed quite a few bugs and added some significant enhancements
since Apache Commons Configuration 2.7 was released, so I would like
to release Apache Commons Configuration 2.8.
Apache Commons Configuration 2.8 RC1 is available for review here:
