Since I was the one who advised Nikita to stick with M5, let me comment on 
this. I am aware that many projects at Apache increment their build numbers 
upon failed votes. I just felt there wasn't really any logical justification 
for it in our case, and we'd be doing it entirely out of puristic reasons. 

> For the future, we should never "unrelease" anything. 


I agree with "no unrelease", but we haven't "released" anything yet. We just 
posted some files for review. 

> Since you didn't delete the artifacts I already downloaded to my machine, 
> there is confusion.

PMC members know exactly what happened. So I don't think that's a problem for 
them. And if we are concerned about an outside person who may have downloaded 
those artifacts, then I don't think that renaming the final set to M6 would 
make any difference. In both cases someone would get stuck with a signed but 
unapproved copy of M5.

The only remotely possible cause for confusion that I can think of is if an 
outside person used that temporary Maven repo, and now the M5 artifacts are 
stuck in his local ~/.m2/repository and they need a manual refresh. Again, I am 
hoping this won't confuse any of the PMC members. 

Andrus


> On Feb 25, 2017, at 3:58 AM, Aristedes Maniatis <a...@maniatis.org> wrote:
> 
> I agree with Mike. Since you didn't delete the artifacts I already downloaded 
> to my machine, there is confusion. For the future, we should never 
> "unrelease" anything. At the very least, please post hashes of the new files 
> to this mailing list.
> 
> There is no shame in releasing 10 milestones if that's what it takes.
> 
> Ari
> 
> 
> On 25/2/17 2:20am, Nikita Timofeev wrote:
>> Hi, Mike
>> 
>> Release is still only 4.0.M5, v2 is only to distinct mail threads.
>> And I have deleted previous builds, so there should be no confusion.
>> 
>> On Fri, Feb 24, 2017 at 6:08 PM, Mike Kienenberger <mkien...@gmail.com> 
>> wrote:
>>> It seems like it may make more sense to change the version to M6 rather
>>> than create M5-v2 and have to deal with potential confusion.
>>> 
>>> On Fri, Feb 24, 2017 at 3:54 AM, Nikita Timofeev <ntimof...@objectstyle.com>
>>> wrote:
>>> 
>>>> Hi all,
>>>> 
>>>> I'm published new files for 4.0.M5 release and you can start voting
>>>> (again).
>>>> The only difference should be fix for CAY-2242.
>>>> 
>>>> Here are links:
>>>> Maven: https://repository.apache.org/content/repositories/
>>>> orgapachecayenne-1013
>>>> Assemblies: https://dist.apache.org/repos/dist/dev/cayenne/4.0.M5/
>>>> 
>>>> Sorry for inconvenience, hope this one will be promoted to the official
>>>> release.
>>>> 
>>>> --
>>>> Best regards,
>>>> Nikita Timofeev
>>>> 
>> 
>> 
>> 
> 
> -- 
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A

Reply via email to