[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: conflict resolver status update (roll 1.10.0 alpha 1?)

From: Stefan Sperling <stsp_at_elego.de>
Date: Tue, 24 Jan 2017 18:45:37 +0100

On Tue, Jan 24, 2017 at 05:08:51PM +0000, Daniel Shahaf wrote:
> Stefan Sperling wrote on Tue, Jan 24, 2017 at 12:20:39 +0100:
> > I would like to get an 1.10.0 alpha1 released in February. Unless I hear
> > objections I will start rolling this alpha release from trunk and call a
> > vote on it soon.
> That all sounds good.
> However, last time we did that we had barely any feedback. How do we
> plan to change that this time?
> Maybe some combination of
> - Posting on users@ or announce@ soliciting testing

Yes! I hope we can motivate some of our power users to compile the
release and test it.

> - Asking downstreams (distros) to make alpha1 packages easily available to opting-in users

Yes we can do that. But this is often ineffective because distros already
have enough work to do as it is.

What is more effective is that those among us who maintain packages put
in some extra effort in providing them. E.g. what I could do is provide
RPMs SUSE users could install from the OpenSUSE build service.
> - Asking client authors to make alpha1 versions easily available to opting-in users
> [e.g., tsvn nightlies — and then call for tsvn users to install them...]

One goal of making an alpha release is to encourage third parties such
as TSVN to start looking at updating their clients. I don't think much
has happened there so far.

> We should be clearer in these communications about the implications of
> using an alpha, i.e., the "use it only on wc's you can re-checkout, and
> not on the server-side" warning.

Sure. We have always had such warnings for alphas as far as I remember.
Received on 2017-01-24 18:45:57 CET

This is an archived mail posted to the Subversion Dev mailing list.