Fixed user facing bugs.
Found via `codespell -S "*.desktop,*.diff,./intern,./extern,./locale,./AUTHORS,./source/blender/blenlib/tests/BLI_string_utf8_test.cc,./doc/license/bf-members.txt" -L accessort,abd,aci,alo,ans,ba,bording,childrens,clen,constructin,datas,dependees,domin,eary,ege,eiter,elemt,eles,enew,espace,finded,fiter,fpt,groupd,hist,implementating,indext,ine,infront,inout,inouts,inpt,ist,lene,listenter,lod,maks,masia,mata,mis,mke,nam,nd,ned,opose,ot,outlow,parm,parms,passt,pinter,pixelx,poin,pres,ptd,re-usable,re-use,re-used,re-uses,re-using,ridiculus,schem,soler,strack,suh,te,tesselate,tham,ue,vai,varius,wew`
Pull Request: https://projects.blender.org/blender/blender/pulls/145825
This commit makes a few small changes to the bug fixes per release
script:
- The main loop is factored out into it's own function, making it
easier for external scripts to reuse.
- The cached commits file has been renamed to include the range
that is cached. This allows multiple caches to be kept for situations
where you're collecting a list for both the current release and main.
- The Blender 5.0 example has been updated with the 4.5 backport task.
Pull Request: https://projects.blender.org/blender/blender/pulls/141867
This commit adds a feature to the bug fixes per release tool to ensure
the version numbers of the backported Blender versions are in ascending
order.
Before: 4.2.9, 4.4.1, 4.2.9
After: 3.6.22, 4.2.9, 4.4.1
Pull Request: https://projects.blender.org/blender/blender/pulls/139011
In a previous commit (1) a feature was added to the bug fixes per
release script that prompted users if they want to sort revert commits.
This commit removes this feature, instead preferring that revert
commits are sorted in the overrides task (blender/blender#137983)
This was done because:
- The overrides task allows for greater control over how revert commits
are classified, and it's synced between all users.
- The prompt to sort the commits appearing each time the script is run
is annoying for triagers who may run the script multiple times in one
day as they sort through various commits.
(1) blender/blender@9679d9a3eb
Pull Request: https://projects.blender.org/blender/blender/pulls/138505
This commit improves the grammar when reporting which versions of
Blender a commit was backported to in the "bug fixes per major release"
script if it was backported to 3 or more verisons of Blender.
Before:
- Backported to 3.6.22 & 4.2.9 & 4.4.1
After:
- Backported to 3.6.22, 4.2.9, and 4.4.1
Along with this change, I now use the word "and" rather than the
symbol "&".
Pull Request: https://projects.blender.org/blender/blender/pulls/138500
The script for collecting bug fixes per release have a caching feature
to speed up frequent re-running of the script by triagers to sort
commits.
This commit changes the script so that fix commits that don't have a
known module are no longer cached.
This is done because part of the sorting of commits is making sure
they're assigned to the right module. This typically means checking
on commits with "Unknown" modules and giving them a module label.
However due to caching, triagers running the script won't see those
changes until they clear their cache. To fix this, we no longer cache
commits with unknown modules.
Pull Request: https://projects.blender.org/blender/blender/pulls/138503
This commit update the release note tools to read the crawl delay for
projects.blender.org directly from
https://projects.blender.org/robots.txt instead of relying on a hard
coded value.
The list of bug fixes per release tool has a option to override which
issue a commit fixed (Useful if someone accidentally put the wrong
fix report number in their commit message).
The way the feature was setup previously wasn't that great, requiring
commiting information to the Blender repository, and it was prone to
bad merge conflicts if multiple people worked on it.
This commit fixes this issue by shifting the overrides list to a bug
report in the Blender repository, detaching it from commits to the
Blender repo, avoiding merge conflicts.
Pull Request: https://projects.blender.org/blender/blender/pulls/136750
This adds a small feature to the script that generates a list of
bug reports per release to help users of the script sort reverted fix
commits.
This comes in the form of the script presenting you with the commit
message for each revert commit and asking you what commit hash was
reverted (The hash should hopefully be in the commit message.)
Pull Request: https://projects.blender.org/blender/blender/pulls/137582
In the bug fixes per release tool, we got a list of bug reports that
were fixed by a commit using a regular expression that pulled the
number from `#NUMBER`.
However in specific situations, this resulted in the retrieval of the
wrong issue numbers, and ultimately a mis-classification of a
fix commit.
For example 778b1efd84 contains `Fixes blender/blender-manual#NUMBER`
We were extracting the NUMBER from this and treating it as if it was
a bug report for the `blender/blender` repository, which means it
points to the wrong bug report.
This commit fixes this issue by taking a simple approach of only
checking for report numbers that match the format:
`SPACE#NUMBER`, which will eliminate cases like
`blender/blender-manual#NUMBER`.
Pull Request: https://projects.blender.org/blender/blender/pulls/136744
This commit updates the bug fixes per release script with small changes
to the readme.
- It removes the example script for Blender 4.4 as it's no longer
under development.
- It updates the example for Blender 4.5 to include the 4.4 backports task
Pull Request: https://projects.blender.org/blender/blender/pulls/136224
Occasionally users will fill out a bug report with the fields like:
```
Broken: A
Working: Also Broken in B
```
This can lead to bug fixes per release script classifying the report
incorrectly.
This commit adds a small check that sees if "broken" is in the working
field, and if it is, then avoid adding the versions in that working
field to the list of working versions used for classifcation since we
can't trust it.
Pull Request: https://projects.blender.org/blender/blender/pulls/136392
While sorting reports for the "list of bug fixes for old bug reports",
occasionally triagers have encountered a report that's too difficult or time consum
ng to track down the correct information for.
In cases like this, it was decided that just ignoring the bug report
was a better option, and so this commit adds a option to do this by
adding the string `skip_for_bug_fix_release_notes` to the report.
preferable as `<!-- skip_for_bug_fix_release_notes -->` since it's
invisible.
Pull Request: https://projects.blender.org/blender/blender/pulls/135218
If a user wants to expand the "bug fixes per release" script with
new classifications, it requires them searching for and expanding a few
lists spread through out the code.
This annoying for anyone not familiar with the code, so refactor these
lists out to the "Constants" section to make it easier to see and
expands.
With the transition from 4.4 Alpha to 4.4 Beta and 4.5 Alpha, a few
small changes could be made to the "list of bug fixes per release" tool
to make it more reliable:
- 4.5 is added to the list so it can detect reports made from
Blender 4.5.
- Update the example usage to of the script to be the exact arguments
triagers should use for 4.4 Beta and 4.5 Alpha so triagers just need to
copy and paste the arguments to the command line.
With 4.4 Beta and 4.5 Alpha, small updates to the "list of bug fixes
per release" tool could be made to make the script.
