[ sending to the list to avoid duplicates ] On Mon, Jan 19, 2026 at 08:00:00AM -0800, Otto Kekäläinen wrote:
> Why did you do the commits on a new branch debian/experimental? This is usually done when you want to keep commits for unstable and experimental separate. > Are you thinking those commits were temporary and might be thrown > away instead of being done on the default branch? That's usually the case. > When are you going to merge in on debian/latest? Assuming you are talking about golang-github-azure-azure-sdk-for-go, the branch was created just a few days ago. Is it already necessary to know the answer to that? > Are people who want to make improvements to the package expected to > target MRs on debian/latest or on debian/experimental? You can send the patch to the BTS and let the uploader decide :-) > If you upload from the non-default branch, should you change it to > the repository default branch? Or in the upload add a `-b > debian/experimental` suffix to the debian/control:Vcs-Git line so > that vcswatch can keep track of that real state of the package? I don't think that's necessary if it's a short-lived branch. Now, given that I have been able to answer to most of those questions based solely on common sense any my own use of experimental, I wonder if the above questions are genuine and related to the package at hand, or maybe they are a form of criticism of the use of debian/experimental branches in general. Thanks.
