#2033 Issue closed
: Placeholder for new release of ReaR 2.5¶
Labels: fixed / solved / done
, ReaR Project
gdha opened issue at 2019-02-05 14:38:¶
Relax-and-Recover (ReaR) release 2.5 Preps¶
-
close as many ReaR 2.5 labeled issues
-
decide on some issues to post-pone to a next release
-
verify if there are no blockers for the release
-
check the documentation if it is still accurate for the new release
-
wrap-up the release notes
-
cool-down period to allow testing of the ReaR-2.5 (beta) release
-
decide on a release date
PS: if we miss something please let us know
gdha commented at 2019-02-13 09:48:¶
Update documentation e.g. doc/user-guide/03-configuration.adoc
jsmeix commented at 2019-02-27 08:33:¶
Because of what @schabrolles wrote 3 days ago in
https://github.com/rear/rear/issues/2019#issuecomment-466769572
I don't have a lot of time and will be really busy
till the end of next week
I suggest to postpone the ReaR 2.5 release until @schabrolles
has a bit more time for ReaR according to
https://github.com/rear/rear/milestones
For ReaR release 2.5 we do not have a release date
in mind (beginning 2019). It depends on bug fixes
or bleeding edge new features...
I suggest to postpone the ReaR 2.5 release until end of next week
plus one more week which would be until Friday 15. March 2019
provided that one week is sufficient for @schabrolles
@schabrolles
I would appreciate it if you could before ReaR 2.5 release have a look
at
-
https://github.com/rear/rear/issues/2041#issuecomment-464646710
-
https://github.com/rear/rear/issues/2019#issuecomment-466349187
therein in particular what I wrote about your
refresh udev with trigger before activating multipath
in your
https://github.com/schabrolles/rear/commit/03228ffdbf748e16026d8776c0745b0794c74148 -
https://github.com/rear/rear/issues/2020#issuecomment-458449760
gdha commented at 2019-02-27 16:24:¶
I moved the scheduled release to end of March 2019 - plenty of time to get the last issues in and do the stability tests...
gdha commented at 2019-04-09 11:10:¶
@rear/contributors Shall we try to wrap up rear-2.5 so we can start creating our validation matrix?
jsmeix commented at 2019-04-26 09:01:¶
Right now this is the only open issue for ReaR 2.5
(also no pull requests that we must have in ReaR 2.5) and with
https://github.com/rear/rear.github.com/commit/4bc1a19f6cb4f779d895434e1c32f19d8a09bab1
the release notes for ReaR 2.5 are up to date,
only Version 2.5 (work in progress)
would have
to be changed to Version 2.5
therein
provided we @rear/contributors agree to release
our current GitHub master code as ReaR 2.5.
gdha commented at 2019-04-26 09:50:¶
@rear/contributors Fine - shall we first file up https://github.com/rear/rear/wiki/Test-Matrix-rear--2.5 a bit before we make the general release available. Can we agree on this?
jsmeix commented at 2019-04-26 12:38:¶
I agree with https://github.com/rear/rear/issues/2033#issuecomment-486999654
What I basically meant with
https://github.com/rear/rear/issues/2033#issuecomment-486983987
is that we first agree to freeze our current GitHub master code
so that we can test a non-moving state and then - provided
there are no severe issues - release it as ReaR 2.5.
gdha commented at 2019-05-08 12:09:¶
@rear/contributors Can we pin-point for a release upcoming Friday? If not new blockers appear I would go for that Friday. Please let us review the documentation, man page and web site (download section) before the release to avoid (stupid) mistakes in the documentation...
jsmeix commented at 2019-05-08 13:55:¶
o.k. for me regardless that I will not find time to test our latest
master code
for SLES and openSUSE...
By the way, what about
https://github.com/rear/rear.github.com/commit/84ecf6ab8fafc8f84449b8450ccf084143358fe4#r33420907
jsmeix commented at 2019-05-09 07:34:¶
A side note regarding "review the documentation":
I found
https://github.com/rear/rear/issues/2140
but that is an "RFC" for "Rear future".
jsmeix commented at 2019-05-09 09:11:¶
@gdha
currently on
https://build.opensuse.org/package/show/Archiving:Backup:Rear:Snapshot/rear
all fail because there is no rear-2.4-git.0.f98a187.unknown.tar.gz
e.g. see the build log for openSUSE_Factory/x86_64 at
https://build.opensuse.org/package/live_build_log/Archiving:Backup:Rear:Snapshot/rear/openSUSE_Factory/x86_64
that contains (excerpt):
error: Bad source: /home/abuild/rpmbuild/SOURCES/rear-2.4-git.0.f98a187.unknown.tar.gz: No such file or directory
which is also visible at
https://build.opensuse.org/package/show/Archiving:Backup:Rear:Snapshot/rear
because there is no such file in the list of Source Files
that is
shown there.
gdha commented at 2019-05-09 10:49:¶
@jsmeix I forced a rebuild - it started building again...
gdha commented at 2019-05-16 14:22:¶
As ReaR-2.5 has been released in the meantime we may close this issue.
[Export of Github issue for rear/rear.]