Version Control – Should I accept that a client adds changes to the source code on an ongoing development?

I am currently in a situation (I am a technical manager) where the client has changed the source code itself, and I am told to accept the changes and continue working on this version. Technically, he owns the code, but he decided to make a change and did not inform me.

Its modifications will not follow any convention, no good practice and, because of a reporting requirement, have made a change to the data structure.

My boss told me to accept it and to occupy it. I replied by asking him then why should I impose any standard on my team if a customer ruined everything we took so much effort to maintain the quality of the code.

The customer acknowledged that he would agree to cancel the changes, but data has already been created with this change and canceling these changes would mean losing them.

Regardless of the details, my question remains. Should I accept the fact that the client has modified the source code and that I have to continue with it, or should I remain faithful to the standards of the team and refuse to continue?

Edit: I did some research on the subject but I found only topics on the ownership of the source code.

how to know the version, the configuration files, the open ports and the purpose of the task

how to know the version, the configuration files, the open ports and the purpose of the task.

enter the description of the image here

git – my version of ubuntu is 14.04.4 and i am new to ubuntu. help me please to solve this problem

Reading package lists … Done
Build a dependency tree
Reading status information … Done
The git-core package is not available, but another package designates it.
This may mean that the package is missing, obsolete or
is only available from another source

E: The package & git-core & # 39; There is no candidate for installation

My version of Ubuntu is 14.04.4 and I am new to Ubuntu. help me please solve this problem.

Why is the Postfix version in this operating database entry superior to the latest version of Postfix?

I have browsed the Exploit database to learn more about the types of exploits of a mail server, and I've come across one that I do not quite understand:

https://www.exploit-db.com/exploits/34896

Why does the exploit say that it applies to Postfix version 4.2.x <4.2.8? As I understood on the official Postfix website, the latest version is only 3.4.6.

Also, as I understand it, this exploit must be run on a user with login privileges, correct? Since the exploits of Shellshock are exploits of elevation of privileges.

8 – get the translated version of the current URL token

In D8, with the usual translation modules enabled, a custom pop-up window allows you to change languages ​​on our site. Currently, it contains a link and a text, like this:

EN | ES

It would work, except that the translated page link is different.

Example. If I am on the English page, "website.com/contact-us" and I change my language to Spanish, the page will load "website.com/es-us/contact-us" … which is not the same. ;does not exist. This is a 404 error

But that's wrong. Spanish version is correctly spelled "contáctenos"
So, I want the Spanish user to go to "website.com/es-us/contactenos".

Is there a way to do that with the chips? Or another approach? A way to know to send the user to the Spanish translation of the page in url

Thank you!

magento2.3 – Error while upgrading version 2.2.3 to 2.3.0 of Magento CE with compose?

have tried to use the command below but have errors

Command 1:

Compose need magento / product-community-edition 2.3.0 –no-update

Command 2:

composer's update

Exit:

 Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for magento/product-community-edition 2.3.0 -> satisfiable by magento/product-community-edition[2.3.0].
    - magento/product-community-edition 2.3.0 requires elasticsearch/elasticsearch ~2.0|~5.1 -> satisfiable by elasticsearch/elasticsearch[2.0.x-dev, v2.0.0, v2.0.0-beta1, v2.0.0-beta2, v2.0.0-beta3, v2.0.0-beta4, v2.0.0-beta5, v2.0.1, v2.0.2, v2.0.3, v2.1.0, v2.1.1, v2.1.2, v2.1.3, v2.1.4, v2.1.5, v2.2.0, v2.2.1, v2.2.2, v2.2.3, v2.3.0, v2.3.1, v2.3.2, v2.4.0, v5.1.0, v5.1.1, v5.1.2, v5.1.3, v5.2.0, v5.3.0, v5.3.1, v5.3.2, v5.4.0, v5.5.0] but these conflict with your requirements or minimum-stability.

if anyone has an idea help me … !!!

photoshop – How can I save this "no group" version of this image from ACR?

The sky shows bands in Photoshop, but if I press Ctrl + Shift + A to access ACR, they disappear.

I guess no real pixel is changed when I connect to Adobe Camera Raw and I do not touch any buttons / sliders … it's a preview of the image differently on my monitor. The preview of Photoshop displays the formation of tapes, but not the preview of ACR.

However, if I save the image out of Photoshop and visualize it, the tape is there. It's like I can preview a beautiful sky without a band in ACR, but there's no way to back it up.

https://i.imgur.com/0dTd2KD.png

This link looked exactly like my problem: why do I see a tape with Photoshop but not Lightroom?
BUT … according to the article, the grouping is not really there, it's just a visual artifact due to photoshop taking shortcuts to save memory.

But that does not seem right to me, because if I save the image and then open it, I always see the bandage.

How can I take what I see in ACR and save it in my final file png / jpg / whatever?

PS: I do not know if that counts, but the photo started as a 32-bit HDR .psb file, which I then edited and converted to 16-bit format.

release management – Transition to the semantic version from simple version numbers

There is a software / application / framework library that currently uses "simple version numbers". So he is currently at the version (let's say) 135 and publications are made at irregular intervals whenever "there is enough for a new publication". The next version would be 136 in this scheme.

I want to use this option to use semantic versioning (version numbers and release behavior, of course).

Which version should I use for the "first" semantic version?

That is, if the next version should be 135.1.0 … or 136.0.0. Or 1.0.0? What is the "correct" approach and which approach breaks the least number of version comparison algorithms?

html – tag generates a blue area behind the preformatted text and a table around it on the printable version. How to disable this?

I use Pre tags to embed lines of code into my MediaWiki page. The problem is that the Pre tag generates a blue box behind the preformatted text that is parsed into an array when you set printable = yes in the URL of the page. The question is whether there is a way to change this, change the table in any way, or disable it when printable = yes?

How to update the version of PHP in WordPress?

In wordpress dashboard, the php version it contains is not suitable and suggests me to update the PHP version. Is it really a need to consider or can we just ignore it?