I need to find release notes for Bash from 3 to 4.
I could not find them neither by google.com/linux nor by default google.
I also looked unsuccessfully at gnu.org.
Where are the release notes for Bash?
From Bash website you can download "Bourne again shell (BASH)".
Inside the download you can find the release notes.
EDIT: Or browse the source online, see NEWS for the summaries, and CHANGES for details.
For patch releases, these could be useful:
https://ftp.gnu.org/gnu/bash/bash-4.4-patches/
https://ftp.gnu.org/gnu/bash/bash-5.0-patches/
https://ftp.gnu.org/gnu/bash/bash-5.1-patches/
https://ftp.gnu.org/gnu/bash/bash-5.2-patches/
There are two files distributed with the source: NEWS and CHANGES. CHANGES documents everything, while NEWS summarises new features.
You can find a summary for BASH 4 here, or check out section B1 of the FAQ for the latest NEWS.
Here you go:
http://tiswww.case.edu/php/chet/bash/NEWS
On my machine (Ubuntu 9.04) it's located at /usr/share/doc/bash/CHANGES.gz
Related
Like the documentation of python or django, how do I have multiple versions of my doc with sphinx ?
I saved my doc on git, and I want my user to be able to see documentation for different version like v2.7,v3.4, etc
Thank you for the help
You could just use Read The Docs to host your documentation for you. They automatically handle multiple versions with a dropdown:
https://docs.readthedocs.io/en/latest/index.html
If you'd like to host your own documentation on GitHub Pages or some other web server, I made a Sphinx extension that does what you're looking for:
https://github.com/sphinx-contrib/sphinxcontrib-versioning
There's the sphinx-multiversion extension.
It's similar to sphinxcontrib-versioning, but sphinxcontrib-versioning doesn't seem to be actively maintained. The last release was in 2016, and it doesn't work with more recent versions of Sphinx (issue #77). sphinx-multiversion is a new implementation (see comment by the author).
Note on healthiness of the project: as of December 2020, it seems that SMV is a one-person project and there are a number of open issues and pull requests that haven't been responded to (though see this comment by the author).
Like the documentation of python or django, how do I have multiple versions of my doc with sphinx ?
I saved my doc on git, and I want my user to be able to see documentation for different version like v2.7,v3.4, etc
Thank you for the help
You could just use Read The Docs to host your documentation for you. They automatically handle multiple versions with a dropdown:
https://docs.readthedocs.io/en/latest/index.html
If you'd like to host your own documentation on GitHub Pages or some other web server, I made a Sphinx extension that does what you're looking for:
https://github.com/sphinx-contrib/sphinxcontrib-versioning
There's the sphinx-multiversion extension.
It's similar to sphinxcontrib-versioning, but sphinxcontrib-versioning doesn't seem to be actively maintained. The last release was in 2016, and it doesn't work with more recent versions of Sphinx (issue #77). sphinx-multiversion is a new implementation (see comment by the author).
Note on healthiness of the project: as of December 2020, it seems that SMV is a one-person project and there are a number of open issues and pull requests that haven't been responded to (though see this comment by the author).
I've succesfully generated a docset with AppleDoc by following the installation instructions. If i got into XCode Documentation Organiser, everything is there, including the categories:
But when I ⌥-click on one of my category methods I see nothing but this:
I've tried a lot of things but none of these work:
Adding --no-merge-categories
Adding --merge-categories
Changing filename extensions
Restart XCode
Restart macbook
Search google (AppleDoc quickhelp categories)
Search stackoverflow
Search gitHub repository issue list (https://github.com/tomaz/appledoc)
Please help, because I want to generate documentation, and most of my library consists of categories. I'm using the latest AppleDoc (appledoc 2.1 (build 858)), and Xcode 4.6.3.
Edit: are there users actually using AppleDoc? Does the quick help actually work for you? I also note a lack of documentation even though the repository is updated regularly.
It seems nobody else is using appledoc but me. Anyway, it looks like it is a bug in XCode, i have pushed a workaround in github. Comment if you want details.
Update: my pull request has been accepted, check here for details:
Pull request https://github.com/tomaz/appledoc/pull/375
related issue: https://github.com/tomaz/appledoc/issues/374
I'm trying to understand how to use GIT with Xcode 4.2.
I haven't been using GIT actively, but while I was walking through a couple of git operations mentioned in this link it appears that I have a single repository with many projects in it and a recent project in a repository all by itself.
I want to carefully take the project I am currently working on and put it into its own repository so I can safely leverage some of the branching capabilities.
I'm hesitant to begin until I have a better understanding of what's going on. I'd like to know how much is handled within Xcode and what I have to do at the command line.
#manojids comment to learn a source control system (like git) outside of a specific editors integration is a good point. Try to understand the source control system. The integration is a convenience, not a crutch.
Outside of that advice, apple has some docs outlining specifics of how XCode works with git. Here's the link:
http://developer.apple.com/library/mac/#documentation/ToolsLanguages/Conceptual/Xcode4UserGuide/SCM/SCM.html
A good online resource is the pro git book available here:
http://git-scm.com/book
If you want to learn and understand Git and its concepts in detail then this book would be best for you here is the link.
Or you can have a drill on it practically if you follow this tutorial.
I hope you will get help.
I wrote gem and published it to github (ex - https://github.com/randx/six)
I added LICENSE file.
I often see VERSION file in other repo - whats the goal?
Any other files should I add?
Chapter 8 of "Ruby Best Practices" by Greg Brown exclusively deals with properly maintaining Ruby projects, including directory layout, files you should include etc. The book is legally available online here:
http://majesticseacreature.com/rbp-book/pdfs/rbp_1-0.pdf
I always love a good README. It's much easier to read a well explained README than browse the automatically generated RDoc manual. The README should explain what the gem does and how to use it, with example code and even some advanced examples can be included towards the end of the README.
Another essential file is a history or CHANGES file. This file should contain an explanation of the major changes between releases. It does not need to include nitty gritty details, but should include enough information so that someone upgrading from version x to version y can quickly see what's new (so you can asses the benefits of upgrading) and what has changed (so you can asses the potential impacts an upgrade has on your current code).
Too many times I see projects where the CHANGES file is missing, and you're left pretty much in the dark about what has changed when you run an upgrade.
From my perspective each GitHub project (based on your question you have a repo there) should have:
Integration with CI servers (Travis CI, Circle CI, etc)
.github folder with issue/pull requests templates (example https://github.com/zold-io/zold/tree/master/.github)
.gitingore to avoid accidentally committed temporal/local files
.gitattributes for custom Git repo configuration (more https://git-scm.com/book/en/v2/Customizing-Git-Git-Attributes and https://git-scm.com/docs/gitattributes)
.rubycop.yml
Add the following badges to your readme.md
version of your ruby gem
license details
commit activity per year to hightlight the status of the project
More about HoC here https://www.yegor256.com/2014/11/14/hits-of-code.html
the status of the latest builds
the status of dependencies (obsolte or not)
show the vulnurabilities count(if any) for the dependencies
as code quality badges
Projects from the examples above:
https://github.com/dgroup/docker-unittests (java)
https://github.com/mattbrictson/gem (ruby)