cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Nalley <>
Subject Re: release artifact 4.4.1 faulty. How to resolve?
Date Sat, 01 Nov 2014 21:22:44 GMT

We are talking about whats in:
If so, I am not sure how we arrive at the fact that the release
artifacts aren't what we voted on. I looked at the commit log for the
part of the tree and found [1]. I also checked it out, and svn log-ed
it and get the output in [2].

So let me step back and ask - how did you determine that what's in
dist.a.o doesn't match what we voted on? OR -are we talking about
something else?



On Sat, Nov 1, 2014 at 3:12 PM, Daan Hoogland <> wrote:
> People,
> It seems the uploaded artifacts on the release repo of apache does not
> contain the commit-id of the voted release. I don't know if this can
> be remedied. I think we should pull it, right? can we replace it by
> artifacts that do contain the right version? Or should we have a new
> version?
> thanks,
> --
> Daan

View raw message