I was going to wait until the end of the week before discussing this,
but since you brought it up:
I don't think the changes that have been made thus far are significant
enough to warrant another release candidate. I would only go to another
release candidate if we had fixed bugs which were big enough to either
prevent people from testing the release candidate (such as the build and
install bugs we found in rc1) or were likely to raise new bugs (the
spacing change in rc1, which did have some cascading effects which we
were able to track down before going to rc2).
However, I would give the user base a bit more time to test rc2 before
going to general release. The list has been quiet about it, which may
mean that no one's testing it, or that it's working fine. I think that
Henry's idea of scheduling the release date is a good idea. It lets
people know that we think we've got a finished product nearly ready, and
also gives them a chance to put in a few more tests, or report an issue
they've spotted but not had the chance to report yet.
✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝
Br. Samuel, OSB
(R. Padraic Springuel)
PAX ☧ ΧΡΙΣΤΟΣ
_______________________________________________
Gregorio-devel mailing list
[email protected]
https://mail.gna.org/listinfo/gregorio-devel
