Re: [BLFS Trac] #22812: mesa-26.0.7

"BLFS Trac" ([email protected] via blfs-book Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.beyond.book
Message-ID <[email protected]>
#22812: mesa-26.0.7
-------------------------+-----------------------
 Reporter:  Bruce Dubbs  |       Owner:  zeckma
     Type:  enhancement  |      Status:  reopened
 Priority:  normal       |   Milestone:  13.1
Component:  BOOK         |     Version:  git
 Severity:  normal       |  Resolution:
 Keywords:               |
-------------------------+-----------------------
Comment (by zeckma):

 26.1.1 has been released, but I'm thinking we should hold off on that,
 until this comes in.

 In the mean time, I think I have a better scheme for handling Mesa
 updates.

 Right now, the scheme is:
 `26.0.1 -> 26.0.7 -> 26.1.1 -> 26.1.<last>`

 The idea behind this was that the first bugfix release will give us a
 somewhat stable but good idea of what bugs are in the newest major/minor
 release.

 I think we could still aim for that while creating a better user
 experience.

 I think going for a scheme like `26.0.<middle> -> 26.0.<last> ->
 26.1.<middle> -> 26.1.<last>` is more stable, less chaotic, and still
 moderately gets us that idea I mentioned, of finding bugs.

 Granted, all-in-all, it's up to the user what version they want to use.
 I'm mostly speaking about this since things can be a bit hectic from the
 last point release to the next major/minor and its bugfix, before going
 radio silent until the very last bugfix release.
-- 
Ticket URL: <https://wiki.linuxfromscratch.org/blfs/ticket/22812#comment:18>
BLFS Trac <https://wiki.linuxfromscratch.org/blfs/>
Beyond Linux From Scratch

-- 
http://lists.linuxfromscratch.org/sympa/info/blfs-book
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.