Non-SaaS Product GIT Branching Strategy
Dear Team, What’s your recommended approach? A non-SaaS product Two repos - Backend and Frontend Current Approach - Dev, QA and Prod Branches Sprint branch (can’t go with feature branch as multiple unlimited APIs and multiple user stories will impact the same set of APIs) created out of Dev and merged into Dev at end of sprint Post each Sprint Dev branch tagged and PR into QA branch Customers are given Docker images generated out of specific tags from QA branch Now comes the fun part- Say customer 1 on Tag v4.3.0, customer 2 on Tag v4.4.0 and product last release is Tag v4.5.0. Current active sprint once complete would be v4.6.0 Developers currently working on active sprint branch for v4.6.0 Bug 1 reported by customer 1 in v4.3.0 Bug 2 reported by customer 2 in v4.4.0 I can extract the specific tag code, make the changes, then manually make the changes in other tags and release to those customers if common bug, or else manually make the changes in active branch also so that next release it’s not missed What if Bug 1 is a Feature for customer 2 who doesn’t need it? So where will I store these changes? Which branch? I want to avoid having customer specific branches as it becomes a big overhead. Suggestions welcome!
How to maintain versioning of backend services
We have developed a app for Microsoft teams and our first version was published on the app store. We are now working on the next version. However we are not sure how we have to submit the new version for team store review without impacting the existing users. For instance, some of our bot commands will behave differently in the new version. If we have only one backend instance running, when we submit it to store team for review we will impact the experience of existing production users as well. Ideally we would follow a blue-green approach to release new features to selected customers, but in this case we are not really sure how and where to differentiate requests coming (mainly through bot communication, since we can add a app version header in web communication) from multiple versions of the app. We thought of creating new set of resources (app registration, bot channel registration etc) on Azure portal but I guess that would be treated as a new app and not a version update. Any ideas or pointers on how to achieve this would be of great help.
New chapters taking all my storage space./How to turn off versioning/delete old versions all at once
(I'm using education version)Whenever I create or edit a chapter in Stream, it automaticly creates a new version for me in onedrive, the problem is, it actually duplicates the file, for example, if the video size is 1GB and I edited the chapter 50 times, then there would be 50 versions of this video file, and the file size would be 50GB, this issue is really bothering me, it basically takes up all 1TB of my storage, someone help plz. it shows 1.08GB if you check on the detail of this file, but if you check the size of the directory this file is in it shows hundreds of GBsFile versions taking all my storage space (Stream)/turn off versioning/delete all versions
(I'm using education version)Whenever I create or edit a chapter in Stream, it automaticly creates a new version for me in onedrive, the problem is, it actually duplicates the file, for example, if the video size is 1GB and I edited the chapter 50 times, then there would be 50 versions of this video file, and the file size would be 50GB, this issue is really bothering me, it basically takes up all 1TB of my storage, someone help plz.
Sharepoint versioning - limit the number of Minor (draft) versions
Hi, My current organisation implemented Teams some time ago. Obviously, using a collaborative tool such as this starts to amass files. We have chosen to implement Check-out and Versioning on a Library. We don't necessarily want to keep many historic copies, but want to ensure edits are not saved unnecessarily, and want the ability to go back/restore if required. We have now reached a point where warning emails are being received "Approaching SharePoint Site Storage Limit". On investigation, I have found one user is happily saving minor versions of his document, currently the 20MB file is taking up 870MB, being 17% of our allocated storage. He doesn't need all these historic copies, and so I want to limit the number of minor versions, my chosen limit being 5 minor versions. I can only find options to limit the number of Major Versions, and the number of Major versions which have associated Minor versions. MS articles state "The maximum number of minor versions between major versions is 511." There is no mention of setting a lower limit that I can find. Is it correct that there is no way to limit the Minor versions? It seems crazy that a user can create a minimum of 100 major versions + 511 minor versions, especially as we are having to work to an enforced storage limit. Why shouldn't anyone be able to limit the minor versions? >>>>>>>>>>>>>>>>>>>>>>>>> This https://support.microsoft.com/en-us/office/how-versioning-works-in-lists-and-libraries-0f6cd105-974f-44a4-aadb-43ac5bdfd247 discusses 'tracking', "Others only track the major versions". What does this mean? Is tracking actually storing/saving, ie only the ability to store major versions? The change in terminology indicates that I could possible switch to Create Major Versions but somehow keep the ability to create Minor Versions, with only Major being tracked. I suspect this is just a poor choice of wording in the article 😞 Out of interest, if I were to attempt to change my library settings from Create major and minor (draft) versions to Create major versions, what would happen? I dare not try as it could potentially wipe out my colleagues (current) minor versions without warning!
Versioning, Sync and Storage in SharePoint/OneDrive
We have noticed a few issues the way Microsoft is creating any version of the documents and consuming the allocated tenant storage. Here is what I did: I create a new document in a version enabled document library in an SPO Teamsite(with Group) and sync the same document library to my desktop using OneDrive desktop app. I co-author on the document with other users. Problem 1 During Co-authoring, SharePoint creates multiple versions of the document. Every version of the document is consumed from the total storage quota allocated on the SPO site. If a 50 MB document has 500 versions(the default document library limit), it would consume 25 GB from the Site storage quota. Problem 2 For every change in the document, OneDrive is downloading the full file to desktop instead of only the changes in the document. Note: The upload of the change in document is working as expected. It is only uploading the change and not the full document.
Disabling versioning without higher access
hi there, I currently have 2 business accounts that are set up on onedrive, one has full priviledges and the other does not. I find versioning totally a waste of online resources and really want to turn it off. Now, i managed to use this script https://www.spguides.com/sharepoint-online-powershell-disable-versioning/ via Powershell for one of the accounts, the one where i have a full fledged account, and that's great. The other account though which i also need, has much less storage and i would really like to disable versioning. I asked someone to do that for me but not sure she can do it. Having said that, is there another way for disabling versioning? if i go to the settings on the website you only get: and that's kinda the problem. when i run the Powershell script i get: Execute Query - Access denied,. You do not have permission to perform this action or access this resource. Is there any other way for achieving this at all??? Once again, the powershell trick worked on one account and no versions are live now (tested) and it's great, but on the other, no luck with the same command. I checked every single setting and cannot find anything. many thanks, Gabrio
