We'll definitely hold off for further feedback.

Naming logic makes sense to me.

As far as binary files in /dist/dev go, my preference (not a strong
preference) would be to have the zip/tar/rpm as part of the reviewable
materials just so we can catch any errors with those as early as
possible, even if most people focus on the source. Perhaps we should
split things up, e.g.

  dist/dev/daffodil/2.1.0-rc2/{src,bin}/

so as to make the src/bin differentiation more clear and reduce any
confusion.

Thanks,
- Steve

On 02/08/2018 01:24 PM, John D. Ament wrote:
> Well, before starting a new let's review the existing.  I would like a bit
> of time to review the whole release archive.
> 
> What you mentioned is correct, effectively anything on the /dist/dev should
> comply with the package naming scheme.  You should consider whether or not
> you want to put everything on /dist/dev (we tend to recommend only the
> source release goes there, to avoid confusion).  When projects do stage
> other artifacts there, they should all be named the same way.
> 
> I have a long standing disagreement with many IPMC members.  I tend to
> follow the release requirements very closely and push back on an over
> assumption of the requirements.  Most projects implement the -incubating
> suffix as a part of the version #, but that's not required.  So my
> interpretation is that maven distributions do not need to include
> -incubating.  We have set this precedent before with Apache Groovy where
> only the source release was staged and voted upon, the actual maven central
> distribution omitted the -incubating and I'm in full support of that
> approach.
> 
> John
> 
> On Thu, Feb 8, 2018 at 12:58 PM Steve Lawrence <[email protected]> wrote:
> 
>> Multiple issues have been found with this release, so I am officially
>> canceling this vote. We would still ask for continued review of the
>> 2.1.0-rc1 release so that any issues found can be fixed in the 2.1.0-rc2
>> release.
>>
>> Thanks,
>> - Steve
>>
>> On 02/08/2018 11:30 AM, Steve Lawrence wrote:
>>> Hi all,
>>>
>>> I'd like to call a vote to release Apache Daffodil (Incubating)
>> 2.1.0-rc1.
>>>
>>> All distribution packages, including signatures, digests, etc. can be
>>> found at:
>>>
>>> https://dist.apache.org/repos/dist/dev/incubator/daffodil/2.1.0-rc1/
>>>
>>> Staging artifacts can be found at:
>>>
>>>
>> https://repository.apache.org/content/repositories/orgapachedaffodil-1000/
>>>
>>> This release has been signed with PGP key 033AE661, corresponding to
>>> [email protected], which is included in the repository's KEYS file.
>>> This key can be found on keyservers, such as:
>>>
>>> http://pgp.mit.edu/pks/lookup?op=get&search=0x033AE661
>>>
>>> It is also listed here:
>>>
>>> https://people.apache.org/keys/committer/slawrence.asc
>>>
>>> The release candidate has been tagged in git with v2.1.0-rc1.
>>>
>>> For reference, here is a list of all closed JIRAs tagged with 2.1.0:
>>>
>>>
>> https://issues.apache.org/jira/browse/DAFFODIL-1864?jql=project%20%3D%20DAFFODIL%20AND%20fixVersion%20%3D%202.1.0%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
>>>
>>> For a summary of the changes in this release, see:
>>>
>>> https://daffodil.apache.org/releases/2.1.0/
>>>
>>> Please review and vote. The vote will be open for at least 72 hours
>>> (ends on Sunday, 11 February 2018, 12 Noon EST).
>>>
>>> [ ] +1 approve
>>> [ ] +0 no opinion
>>> [ ] -1 disapprove (and reason why)
>>>
>>> My vote: +1
>>>
>>> Thanks,
>>> - Steve
>>>
>>
>>
> 

Reply via email to