tag 1018173 + wontfix
thanks
Hi,
Am 26.08.22 um 15:55 schrieb Itaï BEN YAACOV:
1. I understand that unstable is the place to stage pre-release software. But
this
does not mean it must only contain such. Moreover, given Debian's slow release
cycle
some users (such as myself) use it for daily work, rather than for testing new
software.
Come on, it's not as if I uploaded alphas or betas to unstable. Just RCs.
2. I am **guessing** that you might answer that the last release candidate in
each
cycle is the final release -- but this is merely a guess (is it, actually?)
It is. It is a exact copy of the last release. This is also why 7.4.0
internally is 7.4.0.3 (aka 7.4.0 rc3).
The point is that this is developer logic, but from the point of view of a user,
just being told "this is the final 7.something.whatever release" is so much
easier
and does not involve any guesswork. (Also, you know it when it is uploaded,
rather
than when the first candidate for the next release is uploaded).
Untrue. https://wiki.documentfoundation.org/ReleasePlan/7.4 (as was also
for 7.3) is a clear plan on whet will happen when.
If the final release is indeed equal to some rc#, then, as pointless as this
may seem
to you, could you please just bump up the version number and upload again as
final?
And do a fuill build cycle on all architectures just for this? No.
Would you want to upload a release just to replace it with the next rc
when it gets out? Even more unneeded build cycles.
Here it would be directly one week.
(And here 7.4.1 rc1 was there when 7.4.0 rc3 was in the poppler transition.)
Would you want *only* upload of releases? Thus e.g. not getting all the
bugfixes in 7.4.1? That would be the consequence. I'll then tell you on
any bug "try the version in experimental, since that one is developed".
Do you want that instead?
Note that at some point in time I'll stick to releases, let alone for
the freeze.
Regards,
Rene
