I wanted to get some feedback on opinions of how to manage a potential 
different set of releases....

Our testing group at Lenovo may not line up as well with the 'main' release 
cycle, so we were thinking of actually doing releases on a different cycle.  
Still use the same github repo, just test on a slightly different cycle...

For example, maybe we would release a 2.10 point release with backported fixes 
from 2.11 prior to release of 2.11.  Nothing too dramatic, just a relatively 
conservative way to get fixes into the most recent stable branch on our 
schedule....
------------------------------------------------------------------------------
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user

Reply via email to