This is a public URL from the community that the community decided not to publish to avoid misunderstanding and confusion during the installation. If the procedure is correctly updated to reflect that plus the information Thomas Gerbet and Manuel gave you, I think we can accept it.
This process is of course community driven and discussion about the PR will probably occur and only integrators can give their final approval.

Thomas and Manuel,
Thanks for telling me how to be linked to a stable version of Tuleap, which was my first request.

Thomas, I don't understand why you suggested me to update the installation procedure since Enalean has choosen to not inform users about this possibility.

Regarding request #10620, it seems there there were contributors that introduce this functionnality without any possibility to disable it, which is really embarassing me.

I understand you concerns but I don't really know what to do there.

Maybe you expect that Enalean will develop the feature / option for free, we won't do that. We don't have a infinite budget to please everyone. When we can answer the community questions without too much work we are doing it with great pleasure (like here, were you got your problem fixed for free in less than 3 hours) but when we need to invest time for analysis or development, we just cannot do that.

Jean-Louis, if your upgrade is successful and you are satisfied with the repo I linked, we can probably end the discussion here.
I invite you to develop your needs on each tickets you opened and for more general talk about tuleap development we have a mailing list and a chat, feel free to participate :)

Manuel,

Regarding request #10620, it seems there there were contributors that introduce this functionnality without any possibility to disable it, which is really embarassing me.

My remarks on our contribution to Tuleap was regarding previous requests, by example :

I agree that those proposal make sense.

But, so far, I'm afraid there are no contributors that had an interest to invest (time or money) on that.

Manuel,
My remarks on our contribution to Tuleap was regarding previous requests, by example :
> request #3146
> request #5705
> request #6681
> request #10193
> request #10620

I was able to upgrade to Tuleap 9.12 using the "yum clean all" command.

Jean-Louis,

It's not a matter of company size or whatsoever. There is no fundamentaly better choice between "master" and so called "stable" repositories.

As stated by @tgerbet 

• master receives continuous imporvements and bug fixes
• stable is a monthly snapshot of master at a given date

Choosing between the 2 is a tradeoff between "no changes" (stable url) that also mean no bug / security fixes versus "more changes" bug fixes + new features.

We don't publize 2 URLs in the installation guide because we don't want to clutter this procedure. More options means more questions and we are already answering a lot of questions (for free) with the "simple" procedure.

Now we don't pretend being the best possible tech writers so if someone can propose something simple with more options we are eager to ear this proposal.

 

Ok, just run "yum clean all" before re-running the upgrade procedure.

I am currently using Tuleap™ version 9.11.99.95 on CentOS 6.

I am using Tuleap (formerly Codendi) since seven years.
Our company, MESULOG (www.mesulog.fr), is even smaller than ENALEAN.
I tried to contribute through suggestions and feedback. I let you discovered them. Many of them didn't receive a reply.
If you want to improve your product, at least take into account the remarks of people using it...
Regards,

Which version are you currently using?

The repository you mentionned does'nt work for me :
https://tuleap.net/pub/tuleap/yum/rhel/6/stable/x86_64/tuleap-9.12.99.2-1.el6.noarch.rpm: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"

Tuleap is a libre project so this is the role of everyone to maintain documentation (and code and everything related to this project) if they think it can be improved :-)

Please however note that the name of the repository is probably not well chosen and should probably be renamed as something like "monthly milestone". That's why this repository is not specified in documentation.
Packages in this repo are just a snapshot when we tag the monthly release nothing more. They do not receive security fixes nor critical bugfixes until the next monthly upgrades. If do not find the community repositories stable enough for your use case, Enalean offers the Tuleap Enterprise service which include access to maintenance version of Tuleap where bugfixes and security fixes are backported.

I just wanted to inform you that the installation procedure doesn't mention the stable repository.

Is it the role of the users to define Tuleap's installation procedure ?

Thank you Thomas.

I think that the installation procedure 'http://tuleap-documentation.readthedocs.io/en/latest/installation-guide/full-installation.html' should mention this stable repository.

You have to change your URL in /etc/yum.repos.d/tuleap.repo from the dev ones to the stable ones (https://tuleap.net/pub/tuleap/yum/rhel/6/stable/x86_64/)

Thanks Marie-Ange.

And how can I be sure to upgrade to a stable version, instead of a daily build ?