#379: Python simfactory branch has a confusing name -------------------------+-------------------------------------------------- Reporter: hinder | Owner: mthomas Type: defect | Status: new Priority: minor | Milestone: ET_2011_11 Component: SimFactory | Version: Resolution: | Keywords: -------------------------+--------------------------------------------------
Comment (by knarf):
Using /trunk is the "right" solution in the sense that this is what the development version should be anyway. Whoever wants something 'stable' should use another branch: one of the ET branches quite probably. Now, that this might not be the case for a lot of users might be an issue. As far as I can tell, no development happens in trunk right now. So, I propose:
a) Give people a warning that the version in /trunk will be changed to the python version. The simfactory/Cactus/ET users mailing lists spring to mind. b) Actually do that after some time (maybe a month)?
After that, version 1 would only be available as old release branches (e.g. old ET branches), and /trunk could again be used for the usual development, removing PYSIM_2010.