 |
 |
Dear all, I have undone the tag again, because we have discovered a fatal bug. Our inability to come out with a stable tag really starts be be silly and we clearly need to do something about this. An automated test suit would be an ideal solution, but this will probably take some time to develop. For the next release I will try to come out with some sort of release checklist, and the commits will be tagged only after successfully meeting all the conditions on the list. It won't really solve the technical problems but formalizing it a little bit may at least help us make sure that we have done all the tests that we can do. In the mean time, please treat the commit adc3302a569de0a503bac13e7aef74b7314d31e0 as if it was a release tag, incorporate into your frameworks and do all the tests you normally do. Lukasz 2011/3/24 Lukasz Janyst <[log in to unmask]>: > This is an automated email from the git hooks/post-receive script. It was > generated because a ref change was pushed to the repository containing > the project "xrootd". > > The annotated tag, v3.0.3 has been deleted > was 11f7e5d7f1340fb6faf506b29e79b07ffcb29ded > > ----------------------------------------------------------------------- > tag v3.0.3 > > Tagging v3.0.3 > e11b016f7121ca01958470fefe11522faada36d7 Use macro __SunOS_5_10 instead > ----------------------------------------------------------------------- > > > hooks/post-receive > -- > xrootd >