[Rock-dev] Fixing documentation in branch stable
Leif Christensen
leif.christensen at dfki.de
Tue Jun 11 11:25:35 CEST 2013
Hi,
could you please clarify the process on how to fix documentation, if the
suggested change applies also to 'higer' branches than only stable?
Docu says:
> The guideline is that anything that applies to stable should be done on the stable branch as it is what new rock users see in the first place.
Talking to Alex it seems that the proper way would be to
- switch branch to master
- do your bugfixes there
- push to master
- cherrypick the changes for stable
If so, I guess the documentation for contributing to the documentation
should be clarified.
Regards,
Leif
--
Leif Christensen
DFKI Bremen
Robotics Innovation Center
Robert-Hooke-Straße 5
28359 Bremen, Germany
Phone: +49 (0)421 17845-4149
Fax: +49 (0)421 17845-4150
E-Mail: leif.christensen at dfki.de
Weitere Informationen: http://www.dfki.de/robotik
-----------------------------------------------------------------------
Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern
Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster
(Vorsitzender) Dr. Walter Olthoff
Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
Amtsgericht Kaiserslautern, HRB 2313
Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
USt-Id.Nr.: DE 148646973
Steuernummer: 19/673/0060/3
-----------------------------------------------------------------------
More information about the Rock-dev
mailing list