Check out previous commits to get an overview of what a new release entails.
The following steps describe how to release a new version (e.g. 8.0.0
),
for instance, from the develop
branch.
What <major>.<minor>.<patch>
means in a specific Areca version (8.0.0
):
major
(a major change or) might contain potencial or expects breaking changes.minor
adds new features with expected backguard compatibility.patch
fixes issues with expected backguard compatibility.Add/Update credit to the author and copyright in each modified file if the file already had that info and was originally created by Olivier PETRUCCI.
Update AUTHORS and COPYING files if any file was modified by a new developer.
history.md
shows the change log (online). ```markdownVersion 8.0.0 (released on 2024-09-21)
Check for new version ...
feature.BUILD_ID
BUILD_ID
is shown in the Areca’s log to identify its build version.
These commands can help to generate a new random value:
javac building/GenerateBuildId.java
java building.GenerateBuildId
Next Areca's BUILD ID: 5682047565851761744L for src/com/application/areca/version/VersionInfos.java
Replace (v7.5) BUILD_ID = 5872222636083894532L;
with (v8.0.0) BUILD_ID = 5682047565851761744L;
in
VersionInfos.java.
VERSIONS
:
VERSIONS
shows the change log in the featureHistory
inAreca Backup - About
(Help
menu >About ...
orPlugins ...
).release("8.0.0", 2024, 8, 21, "Fixed Areca launchers. Support for Java 8 LTS. Fixed broken links to online documentation. Fixed `Check for new version ...` feature. Fixed building pipeline. Add dependency manager. Add some documentation for users and developers.");
month
is a zero-basedint
:new GregorianCalendar(intYear, intZeroBasedMonth, intDay)
or
release("8.0.0", 2024, 8, 21, "Fixed Areca launchers. Support for Java 8 LTS. Fixed broken links to online documentation. Fixed `Check for new version ...` feature. Fixed building pipeline. Add dependency manager. Add some documentation for users and developers.");
version.xml
.
version.xml
allows Areca to discover the new released version with the featureCheck for new version ...
```xml <?xml version=”1.0” encoding=”UTF-8”?>
```
id
is the release version.date
is the release date (month is zero-based).url
is where the Areca’s user can download the new release version.description
is the list of changes that includes this new version.Update the value of VERSION_URL
in ArecaURLs.java
if the location where version.xml
is hosted has changed its location (e.g. due to a repo fork).
Update builds.csv
to track BUILD_ID
s (month is one-based integer).
Commit changes to develop
branch:
git commit --message "Version 8.0.0"
Upload release bundles to the url
pointed in version.xml
.
main
branch:git checkout main
main
branch:git pull
develop
into the main
branch with a merge squash:git merge --squash develop
git commit --message "Version 8.0.0
- Fixed Areca launchers.
- Support for Java 8 LTS.
- Fixed broken links to online documentation.
- Fixed `Check for new version ...` feature.
- Fixed building pipeline.
- Add dependency manager.
- Add some documentation for users and developers."
git tag -a v8.0.0 --message "Version 8.0.0
- Fixed Areca launchers.
- Support for Java 8 LTS.
- Fixed broken links to online documentation.
- Fixed `Check for new version ...` feature.
- Fixed building pipeline.
- Add dependency manager.
- Add some documentation for users and developers."
git push --follow-tags