dmbcs/guile
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

*** empty log message ***

Browse source
This commit is contained in:
Jim Blandy 1999-08-30 07:02:46 +00:00
commit ebc4e6cc6a
2 changed files with 26 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

38
RELEASE
View file

@ -7,12 +7,7 @@ absinthe, etc. However, the first release containing the module
system should be called Godot: "This is the one you've been waiting
for."
In release 1.3.2:
* Release is titled ``wormwood'' release.
* remove #/ syntax
* Remove SCHEME_LOAD_PATH.
In release 1.3.6:
In release 1.3.4:
- remove hook support from boot-9.scm
(only provided for backward compatibility)
- remove names evalext.c: serial-map,
@ -76,18 +71,19 @@ Julian Satchell <satchell@merry.dra.hmg.gb>:
version number should be of the form N.M for a major release, and
N.M.L for snapshots and beta releases; L should be even for beta
releases, and odd for snapshots.
6) Set up README appropriately for the release; check name spellings
6) Make sure the downloading addressess and filenames are current.
7) Set up README appropriately for the release; check name spellings
in THANKS, and reformat.
7) Choose new interface numbers for shared libraries.
8) Do a `cvs update -A', to get rid of any sticky tags.
9) Rebuild all generated files in the source tree:
8) Choose new interface numbers for shared libraries.
9) Do a `cvs update -A', to get rid of any sticky tags.
10) Rebuild all generated files in the source tree:
a) Install the .m4 files where aclocal will find them.
b) Run aclocal.
c) Run automake.
d) Run autoconf.
e) Run autoheader.
10) Commit all changes to the CVS repository.
11) Verify that the disty works, too:
11) Commit all changes to the CVS repository.
12) Verify that the disty works, too:
a) BEFORE doing 'make dist', configure the source tree for build
in the same tree with configuration option --with-threads.
Make sure that readline was enabled correctly.
@ -105,24 +101,24 @@ Julian Satchell <satchell@merry.dra.hmg.gb>:
the distribution on their systems (make the disty available to them
via ftp).
i) If you made any fixes, commit them, and start from a) again
11a) Add "Guile N.M released." entry to ChangeLog, and commit it.
12) Tag the entire source tree with a tag of the form "release_N_M".
13) Copy the tar file over to the GNU machines, and send mail to
13) Add "Guile N.M released." entry to ChangeLog, and commit it.
14) Tag the entire source tree with a tag of the form "release_N_M".
15) Copy the tar file over to the GNU machines, and send mail to
ftp-upload@gnu.org, asking them to put it on prep.
14) Send an announcement message to gnu-announce@gnu.org. Put
16) Send an announcement message to gnu-announce@gnu.org. Put
"Obtaining Guile" first, then a brief summary of the changes in
this release, then "Thanks," "About This Distribution," and
"Nightly Snapshots." If I remember correctly, the moderator will
delay it until the tar file appears on prep. The announcement
text should be mostly taken from Guile's README file.
15) Notify freshmeat.net, although they're probably watching anyway.
17) Notify freshmeat.net, although they're probably watching anyway.
(They got the 1.3 release just fine.) I have no idea if
www.bowerbird.com.au will be something anyone refers to, but Guile
does have an entry there.
16) Tweak the version numbers in GUILE-VERSION, and README to indicate that
18) Tweak the version numbers in GUILE-VERSION, and README to indicate that
the sources are snapshot again. Snapshots should have version numbers
of the form "N.M.L", where L is odd.
17) Start a new section of the NEWS file.
18) Start a new THANKS file.
19) Send mail to majordomo-owner@cygnus.com updating the message you get
19) Start a new section of the NEWS file.
20) Start a new THANKS file.
21) Send mail to majordomo-owner@cygnus.com updating the message you get
when you ask majordomo for "info guile".

9
libguile/ChangeLog
View file

@ -1,3 +1,12 @@
1999-08-30 James Blandy <jimb@mule.m17n.org>
* gh_data.c (gh_set_substr): Revert change of 1999-08-29; bcopy is
not a correct substitute for memmove, because it doesn't handle
overlapping source and destination areas on many platforms.
Overlaps are the primary reason to use memmove in the first place.
* ports.c (scm_ungetc): Same.
* strop.c (scm_substring_move_x): Same.
1999-08-30 Mikael Djurfeldt <mdj@mdj-pc.nada.kth.se>
* gc.c (scm_init_storage): Skip registration of cleanup on systems