GNU RCS (Revision Control System) 5.10.1 is available.
The full announcement was posted to the info-gnu mailing list:
GNU RCS (Revision Control System) 5.10.0 is available.
The full announcement was posted to the info-gnu mailing list:
GNU RCS (Revision Control System) 5.9.4 is available.
The full announcement was posted to the info-gnu mailing list:
On the project page for RCS on savannah, the intro blurb now has a proper link to CVS, as well as a link to the tip jar page.
GNU RCS (Revision Control System) 5.9.3 is available.
The full announcement was posted to the info-gnu mailing list:
Additionally, the main page for RCS on Savannah now notes that GNU RCS is provided under the terms of the GNU GPLv3+. (This has been the case since version 5.8, released 2011-08-30.)
GNU RCS (Revision Control System) 5.9.2 is available.
The full announcement was posted to the info-gnu mailing list:
GNU RCS (Revision Control System) 5.9.1 is available.
The full announcement was posted to the info-gnu mailing list:
GNU RCS (Revision Control System) 5.8.2 is available. RCS is a set of programs to manage multiple revisions of files. RCS can store, retrieve, log, identify, and merge revisions. It is useful for files that are revised frequently, e.g., programs, documentation, graphics, and papers.
The full announcement was posted to the info-gnu mailing list:
GNU RCS (Revision Control System) 5.8.1 is available. RCS is a set of programs to manage multiple revisions of files. RCS can store, retrieve, log, identify, and merge revisions. It is useful for files that are revised frequently, e.g., programs, documentation, graphics, and papers.
The full announcement was posted to the info-gnu mailing list:
The next release of GNU RCS will install a dispatch program. This message is to air some thoughts on it with hopes that feedback can inform further progress. The dispatch program is called from the shell; its role is to invoke the other commands.
First, the name: grcs. I chose this for two reasons:
Overloading "rcs" is possible, but that would introduce the need to distinguish between "old rcs" and "new rcs" at runtime. A new name is much simpler.
This helps distinguish GNU RCS from other RCS implementations.
That said, i am open to suggestions for another name. Next: the command selection. At time of writing, the following programs have been converted to be invokable by the dispatch program:
Missing is ident(1) and merge(1), the rationale being that they are logically not necessarily tied to RCS. That is, these two are useful outside RCS proper. For example, i can imagine ident(1) being migrated to its own project, in the process unifying implementations from CVS, Subversion, etc, and then adding customization features. (Any budding hackers interested? What are you waiting for?) Likewise, it would be nice to see merge(1) move into GNU diffutils (and furthermore exposed as a shared-object library, if we permit ourselves some wishful thinking...).
The opposing argument (that both these should also be converted) is supported by uniformity and simplicity. These are gut-feel qualities that nonetheless weigh heavily on the aesthetically sensitive. I picture users converting scripts to use "grcs rlog" but not "grcs ident" grumbling about the maintainer's arbitrariness, not having read (or perhaps not having shared in the imagination of) this message, for example. What do people think?
Lastly: standalone compatability. For compatability, standalone executables in $(bindir), such as /usr/bin/ci are installed. These are implemented as simple shell scripts that invoke the dispatch program. (If you wonder why not symlinks, see the GNU Coding Standards, section "Standards for Interfaces Generally".) A new configure script option ‘--disable-standalone-compat’ inhibits their installation, for those ready to make the jump. The plan is to keep the default enabled for RCS 5.x and remove it (and standaldone programs) in 6.x.
Feedback welcome; please write to help-rcs (a gnu dot org address).
RCS 5.8 is available
GNU RCS (Revision Control System) 5.8 is available. RCS is a set of programs to manage multiple revisions of files. RCS can store, retrieve, log, identify, and merge revisions. It is useful for files that are revised frequently, e.g., programs, documentation, graphics, and papers. You can download it from:
Here are the changes since 5.7:
As this is the first (non-pretest) release under new maintainership, a big thanks go to the following people for reporting bugs, suggesting fixes and generally making the transition a smooth experience:
For more information, including online documentation in many formats, please see <http://www.gnu.org/software/rcs/>.
The ninth pretest release of GNU RCS (Revision Control System) is available at: <http://alpha.gnu.org/gnu/rcs/>.
NEWS summary since 5.7.97:
Also, a strange stdio bug appeared after a gnulib update and disappeared after another, several months later. Then it (or something similar) returned, after another, and then once again disappeared, after another. Throughout, my attempts at debugging were stymied by ignorance and sloth (the usual suspects). This is the primary reason this release is so long in coming. In any case, let's hope this is the last one before the actual 5.8 (fingers crossed)...
The eighth pretest release of GNU RCS (Revision Control System) is available at: <http://alpha.gnu.org/gnu/rcs/>.
NEWS summary since 5.7.96:
Barring further reports, we aim to release 5.8 in the next few weeks. I encourage people to join those listed in THANKS, using the testing support, to flush out problems and/or try out the new functionality. Please send bug reports to bug-rcs (at gnu, etc).
The seventh pretest release of GNU RCS (Revision Control System)
is available at:
http://alpha.gnu.org/gnu/rcs/
NEWS summary since 5.7.95:
Additionally, we now use hydra for continuous builds:
NB: The current "Failed" for i686-darwin (from second link)
is due to resource constraints in hydra configuration, i.e.,
"error: unable to start any build" from:
http://hydra.nixos.org/build/854400
rather than a problem with RCS itself; the i686-darwin build
succeeded a couple days ago and will probably sort itself out
sooner or later.
I hope people will join those listed in THANKS, using the
testing support, to flush out problems prior to the 5.8
release. Please send bug reports to bug-rcs (at gnu, etc).
Repo: http://git.savannah.gnu.org/cgit/rcs.git
The sixth pretest release of GNU RCS (Revision Control System)
is available at:
http://alpha.gnu.org/gnu/rcs/
NEWS summary since 5.7.94:
I hope people will join those listed in THANKS, using the
testing support, to flush out problems prior to the 5.8
release. Please send bug reports to bug-rcs (at gnu, etc).
Repo: http://git.savannah.gnu.org/cgit/rcs.git
RCS 5.7.94 (pretest for 5.8) available
The fifth pretest release of GNU RCS (Revision Control System)
is available at:
http://alpha.gnu.org/gnu/rcs/
NEWS summary since 5.7.93:
The first item ("make check" revamped) is most pertinent for
this release. Although the test suite is still incomplete, it
is now much easier to figure out what goes where, add tests,
and run them. You can even "make check" on an installed (5.7)
set of RCS commands.
I hope people will join those listed in THANKS, using the new
testing support, to flush out even more problems prior to the
5.8 release. Please send bug reports to bug-rcs (at gnu, etc).
Repo: http://git.savannah.gnu.org/cgit/rcs.git
The fourth pretest release of GNU RCS (Revision Control System)
is available at:
http://alpha.gnu.org/gnu/rcs/
NEWS since 5.7.92:
If there are no problems, we plan to release 5.8 in a week or so.
Thanks go to everyone who has tried the pretest releases.
The third pretest release of GNU RCS (Revision Control System) is available at:
http://alpha.gnu.org/gnu/rcs/
NEWS since 5.7.91:
The second pretest release of GNU RCS (Revision Control System) is now available for download from:
http://alpha.gnu.org/gnu/rcs/
NEWS since 5.7.90:
GNU RCS 5.7.90 (pretest for 5.8) is now available in directory:
http://alpha.gnu.org/gnu/rcs/
Please be sure to see README-alpha in the tarball.
We will wait two to three weeks for issues to arise, then decide whether to do another pretest release or to jump to 5.8.