@@ -118,7 +118,7 @@ is decided on a case-by-case basis.
118* If there are real breaking changes, the curator team will retain
118* If there are real breaking changes, the curator team will retain
119 more discretion on how long a window to give before dropping
119 more discretion on how long a window to give before dropping
120 packages.
120 packages.
121−* We usually drop all upper bounds and disable packages when we create
121+* We typically drop upper bounds and disable conflicting packages in Nightly after we create
122 a new Long Term Support (LTS) major version.
122 a new Long Term Support (LTS) major version.
123* There are rare cases where an upper bound or build failure are hard
123* There are rare cases where an upper bound or build failure are hard
124 to deal with so then we may disable
124 to deal with so then we may disable
@@ -162,8 +162,8 @@ Note that it is _not_ a goal of LTS Haskell to track the latest
162version of GHC. If you want the latest and greatest, Stackage Nightly
162version of GHC. If you want the latest and greatest, Stackage Nightly
163is your best bet. In particular, LTS Haskell will often—but not
163is your best bet. In particular, LTS Haskell will often—but not
164always—avoid upgrading to the first point release of GHC
164always—avoid upgrading to the first point release of GHC
165−releases (e.g., 8.2.1) to allow further testing and to get the
165+releases (e.g., 8.x.1) to allow further testing and to get the
166−benefits of the first bugfix release (e.g., 8.2.2).
166+benefits of the first bugfix release (e.g., 8.x.2).
168## Adding a package to an LTS snapshot
168## Adding a package to an LTS snapshot
@@ -173,20 +173,16 @@ ending in `.0`), the package set is taken from Stackage Nightly. Therefore, by
173following the above steps, you can get your package into the next major LTS
173following the above steps, you can get your package into the next major LTS
174Haskell release.
174Haskell release.
176−If you would like to get your package added to an existing LTS Haskell major
176+If you would like to get your package added to the current LTS Haskell
177−release (e.g., if `lts-8.9` is out, you would want your package to appear in
178−`lts-8.10`), please do the following in addition to the steps above:
177+major release, please do the following in addition to the steps for Nightly described earlier:
180−* Check that your package can be built with that LTS major version (e.g. `stack build --test --bench --haddock --resolver lts-8.10`)
179+* Check that your package can be built with the current LTS version (e.g. `stack build --test --bench --haddock --resolver lts`)
181* Open up a new issue on the [lts-haskell repo](https://github.com/fpco/lts-haskell/issues/new)
180* Open up a new issue on the [lts-haskell repo](https://github.com/fpco/lts-haskell/issues/new)
182− * Specify the LTS major versions you would like your packages to go into (e.g. lts-8)
183 * Provide a list of packages you would like added
181 * Provide a list of packages you would like added
184 * If relevant, mention any upper bounds that are needed on those packages
182 * If relevant, mention any upper bounds that are needed on those packages
185* Be patient! The LTS releases are less frequent than Nightly. The
183* Be patient! The LTS releases are less frequent than Nightly. The
186 Stackage curators will try to get to your issue as soon as possible,
184 Stackage curators will try to get to your issue as soon as possible,
187 but it may take some time.
185 but it may take some time.
188−* We gradually stop maintaining old LTS major versions, so your
189− request may take longer or be declined if it's for an old LTS.
191## LTS package guarantees and exceptions
187## LTS package guarantees and exceptions