Master

[Jewest]

Updating the master to the latest release version 3.0.0. allowing forked project to easier update the git repo.

[vasbimpikasadi]

HI Jeff,

Please keep any changes to branching downstream, aka your fork. We don't have plans to utilise a master branch.

[Jewest]

Dear Vasileios,

I wanted to share my experience from yesterday. It took me the entire day to update the Yocto layer from version 1.0.0 to 3.0.0. This task could have been completed in just 5 minutes if we followed the standard Git approach.

The ideal process should have been as simple as updating the master branch and checking out the correct tag: job done. However, the actual process was quite different. I had to spend time trying to figure out where an undefined branch was set. I needed to check out version 3.0.0 and essentially reverse engineer all the used repositories and their versions because nothing was properly tagged.

The lack of explanations and missing tags made the update process needlessly complicated. It almost felt like we were using Subversion (svn) instead of Git. I urge you to consider the fact that there are developers relying on your repositories, and I hope we can avoid such frustrating experiences in the future.

[vasbimpikasadi]

Hi Jeff,

First of all, apologies for the confusion our current branching strategy is causing you. First of all, I’d like to point you to our wiki which makes building a lot more simple, using the repo tool: Linux for ADSP‐SC5xx 3.1.0 Landing Page · analogdevicesinc/lnxdsp-adi-meta Wiki (github.com)https://github.com/analogdevicesinc/lnxdsp-adi-meta/wiki/Linux-for-ADSP%E2%80%90SC5xx-3.1.0-Landing-Page

Secondly, I declined your PR because very shortly we’re leaving release branches behind and we’re going to work on a ‘main’ and ‘develop’ branch, with releases being done as branches. As soon as 3.1.0 is out of the door, we’re making the changes.

Therefore a new branch, ‘main’, alongside ‘develop’, will be rebased to 3.1.0 and then we won’t do releases as branches ever again.

I hope that helps.

If not, please let me know how can I be of further help.

Thanks for your interest and feedback, Vas

From: Jeffrey Westgeest @.> Sent: 04 October 2023 10:44 To: analogdevicesinc/lnxdsp-adi-meta @.> Cc: Bimpikas, Vasileios @.>; State change @.> Subject: Re: [analogdevicesinc/lnxdsp-adi-meta] Master (PR #28)

[External]

Dear Vasileios,

I wanted to share my experience from yesterday. It took me the entire day to update the Yocto layer from version 1.0.0 to 3.0.0. This task could have been completed in just 5 minutes if we followed the standard Git approach.

The ideal process should have been as simple as updating the master branch and checking out the correct tag: job done. However, the actual process was quite different. I had to spend time trying to figure out where an undefined branch was set. I needed to check out version 3.0.0 and essentially reverse engineer all the used repositories and their versions because nothing was properly tagged.

The lack of explanations and missing tags made the update process needlessly complicated. It almost felt like we were using Subversion (svn) instead of Git. I urge you to consider the fact that there are developers relying on your repositories, and I hope we can avoid such frustrating experiences in the future.

— Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/analogdevicesinc/lnxdsp-adi-meta/pull/28*issuecomment-1746515530__;Iw!!A3Ni8CS0y2Y!87Kt8_UfG4uHnvpWAV_48CnWus3wvARxtIyhlKJtj0St81-sXulzCNkdTyeaqB2hhJ2jd3kdV5jOcVpHAttoylE3kwLeBqE$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/A2HMYTQATUGVMK4JR755SZLX5UVUVAVCNFSM6AAAAAA5SGAN6CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBWGUYTKNJTGA__;!!A3Ni8CS0y2Y!87Kt8_UfG4uHnvpWAV_48CnWus3wvARxtIyhlKJtj0St81-sXulzCNkdTyeaqB2hhJ2jd3kdV5jOcVpHAttoylE3f2nPZg0$. You are receiving this because you modified the open/close state.Message ID: @.**@.>>