It is rare that we need to update the documentation for old releases. If you 
need to do this, you can create the branch when needed. E.g. if you wish to 
update the PR documentation for the OpenSAF 4.7.x track, you create an 
opensaf-4.7.x branch from by branching out from the 4.7.0 tag.


---

** [tickets:#2048] opensaf/doc: no separate branches for 4.7 and 5.0.**

**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Mon Sep 19, 2016 11:43 AM UTC by Praveen
**Last Updated:** Mon Sep 19, 2016 11:43 AM UTC
**Owner:** nobody


It seems there are no separate branches for 4.7 and 5.0 for documentation.
Even they are not listed in closed brnaches.
Here is output of hg commands:
\# hg branch
default
\# hg branches
default                      189:e4d420f962d3
\# hg branches -c
default                      189:e4d420f962d3
opensaf-4.6.x                181:0a4b9b47c55c (closed)
opensaf-4.5.x                167:650e49539772 (closed)
opensaf-4.4.x                155:81bbe5de2f18 (closed)
opensaf-4.3.x                134:ff16f59fe449 (closed)
opensaf-4.2.x                 98:b97c89fb2890 (closed)



---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to