From: John Levon <movement@us...> - 2003-04-08 21:00:31
Update of /cvsroot/oprofile/oprofile
In directory sc8-pr-cvs1:/tmp/cvs-serv1009
RCS file: /cvsroot/oprofile/oprofile/ChangeLog,v
retrieving revision 1.960
retrieving revision 1.961
diff -u -d -r1.960 -r1.961
--- ChangeLog 8 Apr 2003 20:04:12 -0000 1.960
+++ ChangeLog 8 Apr 2003 21:00:17 -0000 1.961
@@ -1,3 +1,7 @@
+2003-04-08 John Levon <levon@...>
+ * HACKING: describe what happens with oprofile-www
2003-04-08 Philippe Elie <phil.el@...>
* libutil++/op_bfd.cpp: check for #717720 and direct user to
RCS file: /cvsroot/oprofile/oprofile/HACKING,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -d -r1.5 -r1.6
--- HACKING 30 Mar 2003 20:01:00 -0000 1.5
+++ HACKING 8 Apr 2003 21:00:25 -0000 1.6
@@ -97,8 +97,22 @@
occassionally for release, in which case no commits are allowed at all without
agreement of John and Phil. CVS admin changes (-kb, .cvsignore etc.) do not
need a change log, and neither does changes to TODO. If you make a change
-that affects the user (feature improvement, new feature, bug fix, UI change)
-you should enter a short description in the file release-notes/release-<nextversion>
-in the oprofile-www CVS module and commit it. Do not document bug fixes that
-were not in the last released version.
+that affects the user (feature improvement, new feature, bug fix, UI change),
+see the next section.
+The oprofile website
+The oprofile website source is stored in the oprofile-www CVS module, excepting
+the doc/ and srcdoc/ directories, which are updated by hand at release time.
+The visible website (http://oprofile.sf.net/) must always describe the last
+*released* version of OProfile, but the CVS contents should be up to date with
+the CVS code. This means that if you make a user-visible change as described
+in the last section, you should update the files in oprofile-www and commit.
+You can do "cvs update" in home/groups/o/op/oprofile/htdocs/cvs on sourceforge
+to get http://oprofile.sf.net/cvs/, so you can check your changes work (and
+validate: see http://www.htmlhelp.com/tools/validator/).
+Any user-visible change should have a short description in the file
+release-notes/release-<nextversion> in the oprofile-www CVS module.
+Do not document bug fixes that were not in the last released version.