On Fri, Jan 31, 2025 at 7:50 AM Tomek CEDRO <to...@cedro.info> wrote:
> On Fri, Jan 31, 2025 at 1:41 PM Sebastien Lorquet <sebast...@lorquet.fr> > wrote: > > Of course I also tried with the commit before that one, and it didnt > > work either. > > Sebastien, did you try the release packages? Does the problem occur in > the release packages? > > Upstream master is for development purposes, things may get broken for > a while, I would never put my product on a master branch. I concur with this. Products should be based on official releases. That's why we make releases. You don't have to use release tarballs. You could base your work on the release branch if you need to add customizations. There are a few months between releases. This means that if you cannot invest the time and effort to participate in day to day development, you could instead opt to spend a much less amount of time, just once per release cycle, to help with testing the release candidates and reporting breakage before the release becomes official. That will result in much better quality releases. It will also give you a few months at a time of total stability with no or very few upstream changes, and those changes would only be bugfixes or security. While the master branch *should* be kept as stable as possible, it should *not* be a substitute for releases. Hope this helps, Nathan
