Sounds good.
I'll do 0.7.0.1 next week, if no one objects. Probably just one RC, or
maybe not even an RC, given that the branch has pretty much been an RC
for the past 2 weeks.
Melanie wrote:
Hi,
Justin Clark-Casey wrote:
On 07/08/10 16:42, [email protected] wrote:
Hi all,
Would it be ok to make a 0.7.1 release fairly soon based on the current
0.7-post-fixes branch? Over these past 2 weeks there have been several
bug fixes for 0.7 that might be worth a tag of its own.
Could we call this 0.7.0.1 instead? That way, 0.7.1 is still logically the next release branched from master. I think
0.7.0.1 fairly clearly conveys "bug fix release on 0.7".
+1 on micro micro numbers. Or, use 0.7.1-1, 0.7.1-2, like the RPM
packager.
It might be a good practice to start doing this systematically, i.e.
N.x.0 releases featuring feature additions, and N.x.y (y>0) featuring
bug fixes.
We could do this but then we approach 1.0 very rapidly (0.8, 0.9, ...) which would imply some kind of 'completion' and I
think that we're still some way off that point.
We could go into 0.10, 0.11, 0.12, ... but this seems to be confusing for
people.
Agreed, but is IS being done, if it's needed, so can we. But micro
micro (nano?) numbering is better.
Melanie
_______________________________________________
Opensim-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-dev
_______________________________________________
Opensim-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-dev
