trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: November 2015

Re: [trinity-devel] Release plans for TDE are probably to rethink

From: Slávek Banko <slavek.banko@...>
Date: Wed, 25 Nov 2015 19:12:02 +0100
Dne st 25. listopadu 2015 Alexandre napsal(a):
> Hi,
>
>
> I think that the release plans for TDE are probably to rethink, or to do in
> another way.
>

In summary, I would say: changes successfully underway.

>
> As an example, most projects have their users use the stable releases, but
> in TDE, as R14.0.0 was not 100% up to what users expect, many of those
> switched up to Slavek's preliminary stable builds. This is not bad in
> itself to use unstable versions for testing purposes, but I do not think
> that it is the best idea to use it on a production system.
>

There is not much to say. There are three sources:

1) Stable release
 - there are many users who firmly holds only stable release.

2) Preliminary stable builds == source for maintenance releases
 - there is the number of users who use this resource, because it offers a 
good combination of stability and bug fixes. The principle here will always 
bug fixes faster than the stable releases. Likewise, there will always be 
faster support for new versions of the distributions.

3) Nightly builds == source for major releases
 - is especially useful for developers and testers.

This is already a time-proven model. I believe that there is no reason to 
change that.

>
> Also, as it is the case now, R14.0.2 is not said to be released, but you
> can see users complaining (with reasons) that it is very slow to update to
> R14.0.2., mostly because mirrors are not yet in sync with the main server.
>
> I don't know enough about how software repos work, but I think that the new
> release should be blocked for a moment and then be available to users only
> when everything is ready and in sync on mirrors.
>
>
>
> This would allow:
>
> 1. A more consistent release plan
>
> 2.Stop having to deal with users saying that they get kind-of error 404, or
> ultra slow download speed
>
> 3.Reduce Tim's bandwidth costs and load on its servers
>
>
> What do you think?
>

There were important changes, for which I am hoping will have immediate 
benefits for R14.0.2. New redirector on mirror.ppa.trinitydesktop.org is 
prepared to deal with the usual problems in the release of a new version:

1) New version is offered for download at the moment when the package lists 
are updated on a mirror. This also relates with frequent error 404.

2) Overloaded line to the master server. On the new redirector is also local 
cache that is prefilled packages for most of the Debian/Ubuntu distributions. 
Thank to this, packages are available on quick line, even if they are not yet 
fully on the mirrors.

As it turned out, the problem remained for users who have in their apt sources 
stated original redirector on the master server. However, at present, 
together with Tim we are trying to treat this problem!

>
> Have a great day!
>
> -Alexandre

-- 
Slávek