Lieven Govaerts wrote:
> Quoting Daniel Berlin <email@example.com>:
>> I believe it is simply a matter of our release manager not having time.
>> Not that I blame him, it's just that we have no paid, full time release
>> manager, so we get releases when he has time to make them.
>> He hasn't had time lately due to other, higher priority (and rightly so)
> I have only been involved in subversion-dev starting from 1.4 so my view is a
> bit from the outside. As a result some of my observations/ideas may be plain
> wrong, feel free to point them out.
> To start with, I'm very excited about the prospect of upgrading our (at the
> office) Subversion to the 1.4 release. While there aren't many functional
> changes, lots and lots of issues have been fixed, many of them which we
> encounter daily.
> The 1.4 branch was created 2 months ago, no official RC has been released since.
> In fact, lots of new changes (bugfixes) have been merged to the 1.4.x branch
> The fact that our RM (who voluntarely spends some of his free time on this
> project) didn't have time to make the release is one thing, but it shows me
> other - more importants - facts:
> 1. We only have one RM, nobody seems to be able to replace him?
Actually, he replaced the last RM who up and disappeared for a while
(for personal reasons).
The process is documented.
What time is
> needed for someone to learn the skills of releasing svn? Is it fully documented?
AFAIK, It's just herding people and following the checklist we have.
So it is documented. It was documented when he started, but the
documentation wasn't as complete as it is now.
> 2. Making+publishing a release apparently is very a time-consuming manual
> process. Gathering the required signatures for the Windows .zip file proved to
> be very difficult, probably because there aren't many full committers working
> on Windows?
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Jul 10 16:35:34 2006