[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 19:06:13 +0100

On Tue, Jan 24, 2017 at 05:52:39PM +0000, Daniel Shahaf wrote:
> Stefan Sperling wrote on Tue, Jan 24, 2017 at 18:45:37 +0100:
> > On Tue, Jan 24, 2017 at 05:08:51PM +0000, Daniel Shahaf wrote:
> > > - 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.
>
> I wonder if we should delay the release announcement until we can link
> to a bunch of .deb/.rpm/GUIs/* from it. This way, once we do announce@,
> we can hope for a higher proportion of readers to act about it.
>
> (I'm not proposing to change the "no official binary releases" policy;
> just to wait until downstreams have made their own binaries available)

I don't think our own release announcement has any bearing on this.
We can just announce when we're ready. Once binaries become available
they can also announced on our lists (e.g. by replying to the release
announcement mailthread, as has often been done).

If we do this, it would be good to know upfront what kind of binaries
we can expect and should wait for. And that might complicate things.

> > > - 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.
>
> You mean, updating the stable/GA tsvn client to use alpha1 under the hood?

I mean updating TSVN's trunk code to use the new APIs that were added
recently (some as recently as last week).

I don't follow TSVN or other third party clients so I have no idea
who has is been testing these APIs already.
Received on 2017-01-24 19:06:21 CET

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