Versioning info confusion.
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.4k
- Forks
- 252
- Avg merge
- 7d 11h
- Merged PRs (30d)
- 3
Description
Can we please keep the version info up to date? This can be confusing:
./Makefile:PREREL= -beta3
./etc/luajit.pc:version=${majver}.${minver}.${relver}-beta3
./README:README for LuaJIT 2.1.0-beta3
./doc/status.html:This documentation is for LuaJIT 2.1.0-beta3. Please check the <tt>doc</tt>
./src/luaconf.h:#define LUA_LJDIR "/luajit-2.1.0-beta3/"
./src/luajit.h:#define LUAJIT_VERSION "LuaJIT 2.1.0-beta3"
./src/luajit.h:#define LUAJIT_VERSION_SYM luaJIT_version_2_1_0_beta3
is used for any version after beta3. Should it be beta3-20220411 for example or 2.1-20220411?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the version strings in Makefile, etc/luajit.pc, README, doc/status.html, src/luaconf.h, and src/luajit.h. Decide the canonical format for post-beta3 releases, then update all listed occurrences consistently; done means no stale version references remain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- release
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100