id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc 95,Use of tags to identify a specific NEMO release,ros,ctlod,"[[BR]] Hi, I'm not sure if this is the correct place to raise issues like this so please point me in the correct direction if not. I'm concerned about the way in which it seems tags are being used to identify releases of the NEMO code and the effect this has on the ability of groups to collaborate on NEMO work. There are several groups in the UK collaborating on NEMO work. We have all got what we thought was NEMO v2.3 from the repository (the revision tagged nemo_v2_3). However, we've discovered that we all have different versions of the code because it appears that periodically the tags (e.g. nemo_v2_3 and ioipsl/tags/v2_1_1) are being deleted and replaced with something newer. This goes against the function of a tag. Once there has been an official release of code then that tag should never be changed, thereby guaranteeing that everyone gets the same revision of the code no matter when they download it. I look forward to hearing your comments on this. Regards, Rosalyn.",Defect,closed,normal,,OCE,v2,,fixed,OPA v2,