Paul,
At this point we'll consider 0.5.0-rc1 as a training wheels release. 0.5.0
release is what we are aiming to release as the 1st ASF official release.
Thank you,
--
Aaron Radzinski
On Tue, Apr 21, 2020 at 4:47 PM Paul King <pa...@asert.com.au> wrote:
>
> So with respect to point 1. below, is that release going forward to the
> second round of voting to make it official or was it just a practice run?
>
> On Tue, Apr 21, 2020 at 2:53 PM Aaron Radzinski <aradzin...@datalingvo.com>
> wrote:
>
>> Paul, et. al.,
>> Here's the current situation with releases and their emails.
>>
>> 1. Vote email for 0.5.0-rc1 had an incorrect version in the subject line
>> ("0.5.0" instead of "0.5.0-rc1"). Released was voted in.
>> 2. Current release under the vote is "0.5.0". Vote is still on and will
>> end on April 22.
>>
>> NOTE: we adopted a Release Candidate policy for our releases.
>>
>> I don't think we need to cancel anything at this point.
>>
>> Thanks,
>> --
>> Aaron Radzinski
>>
>>
>>
>> On Sun, Apr 19, 2020 at 8:38 PM Paul King <pa...@asert.com.au> wrote:
>>
>>> Performing releases is an important task for a project. Given that it is
>>> a
>>> formal activity, it needs to be very clear what is being voted on and
>>> what
>>> the result was.
>>>
>>> At the moment, we have one email saying "[RESULT][VOTE] Release Apache
>>> NLPCraft 0.5.0" saying it passed and then another [VOTE] email with the
>>> same subject asking for a new vote. For us, while it is fresh, we kind of
>>> know what is going on, but someone looking back at the email history or
>>> future busy team members involved in a range of projects could become
>>> quite
>>> confused.
>>>
>>> I'd suggest replying to the above [RESULT] email with a cancel response
>>> (as
>>> per Furkan's earlier suggestion) to make it clear. I think most email
>>> clients should let you "edit subject" which should let you use the
>>> [CANCEL]
>>> convention but keep it in the same thread.
>>>
>>> For future vote emails, I'd suggest picking a convention that makes it
>>> clear that a new vote has commenced. This could be using rc1 vs rc2 if
>>> that
>>> is part of the artifact names or tag names or as simple as adding "(take
>>> 2)", "(take 3)" to the emails.
>>>
>>> Cheers, Paul.
>>>
>>> On Mon, Apr 20, 2020 at 7:29 AM Aaron Radzinski <
>>> aradzin...@datalingvo.com>
>>> wrote:
>>>
>>> > Furkan,
>>> > I guess it's just my terminology... All I meant is that this release
>>> > contains quick fixes for the issues discovered on RC1.
>>> >
>>> > Thanks,
>>> > --
>>> > Aaron Radzinski
>>> >
>>> >
>>> >
>>> > On Sun, Apr 19, 2020 at 5:57 AM Furkan KAMACI <furkankam...@gmail.com>
>>> > wrote:
>>> >
>>> > > Hi,
>>> > >
>>> > > What does following up on the 0.5.0-rc1 release mean? This seems a
>>> new
>>> > > release candidate with new commits which has a different checksum?
>>> > >
>>> > > By the way, I've written advices about release candidate votes and
>>> > > cancel vote e-mails.
>>> > >
>>> > > Kind Regards,
>>> > > Furkan KAMACI
>>> > >
>>> > > On Sun, Apr 19, 2020 at 3:27 PM Paul King <pa...@asert.com.au>
>>> wrote:
>>> > >
>>> > > > Also, it is usually good to mention the KEYS file location in the
>>> vote
>>> > > > email and that file still needs to be moved, i.e. not be in the dev
>>> > area
>>> > > > but only in the release area even at this stage.
>>> > > >
>>> > > > On Sun, Apr 19, 2020 at 8:45 PM Sergey Kamov <skhdlem...@gmail.com
>>> >
>>> > > wrote:
>>> > > >
>>> > > > > ok,
>>> > > > >
>>> > > > > but note please that valid pgp link is
>>> > > > >
>>> > > > > not
>>> > > > >
>>> > > > >
>>> > > >
>>> > >
>>> >
>>> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/apache-nlpcraft-incubating-0.5.0.zip.sig
>>> > > > >
>>> > > > > but
>>> > > > >
>>> > > > >
>>> > > >
>>> > >
>>> >
>>> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/apache-nlpcraft-incubating-0.5.0.zip.asc
>>> > > > >
>>> > > > >
>>> > > > > Sergey
>>> > > > >
>>> > > > > 19.04.2020 11:21, Aaron Radzinski пишет:
>>> > > > > > NLPCraft-ers,
>>> > > > > > This is the GA release following up on the 0.5.0-rc1 release.
>>> This
>>> > > > mostly
>>> > > > > > addressed issues highlighted by Paul King in [1]. This final
>>> 0.5.0
>>> > > > > release
>>> > > > > > is ready and up for the vote:
>>> > > > > > 1. Apache dist location
>>> > > > > > <
>>> > https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/
>>> > > >
>>> > > > > > 1. Quick link for ZIP tarball
>>> > > > > > <
>>> > > > >
>>> > > >
>>> > >
>>> >
>>> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/apache-nlpcraft-incubating-0.5.0.zip
>>> > > > > >
>>> > > > > > (SHA256
>>> > > > > > <
>>> > > > >
>>> > > >
>>> > >
>>> >
>>> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/apache-nlpcraft-incubating-0.5.0.zip.sha256
>>> > > > > >,
>>> > > > > > PGP
>>> > > > > > <
>>> > > > >
>>> > > >
>>> > >
>>> >
>>> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/apache-nlpcraft-incubating-0.5.0.zip.sig
>>> > > > > >
>>> > > > > > )
>>> > > > > > 2. GitHub v0.5.0 tag
>>> > > > > > <
>>> > > > >
>>> > > >
>>> > >
>>> >
>>> https://gitbox.apache.org/repos/asf?p=incubator-nlpcraft.git;a=tag;h=refs/tags/v0.5.0
>>> > > > > >
>>> > > > > > 3. JIRA resolved issues
>>> > > > > > <
>>> > https://issues.apache.org/jira/projects/NLPCRAFT/versions/12347774>
>>> > > > > >
>>> > > > > > The vote is formal, see voting guidelines here:
>>> > > > > > https://www.apache.org/foundation/voting.html
>>> > > > > > +1 - to accept Apache NLPCraft 0.5.0
>>> > > > > > 0 - don't care either way
>>> > > > > > -1 - DO NOT accept Apache NLPCraft 0.5.0 (explain why)
>>> > > > > >
>>> > > > > > See notes on how to verify release here:
>>> > > > > > https://www.apache.org/info/verification.html
>>> > > > > >
>>> > > > > > The vote will be held for 72 hours and will end on April 22,
>>> 2020
>>> > at
>>> > > > > > midnight MSK.
>>> > > > > >
>>> > > > > > Thank you!
>>> > > > > >
>>> > > > > > 1.https://tinyurl.com/yadhotu2
>>> > > > > > --
>>> > > > > > Aaron Radzinski
>>> > > > > >
>>> > > > >
>>> > > >
>>> > >
>>> >
>>>
>>
