apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Weise <thomas.we...@gmail.com>
Subject Re: creating and updating JIRAs
Date Thu, 30 Mar 2017 15:25:32 GMT
Yep, it isn't the release managers responsibility to clean up JIRA.
Everything should be in place by the time PRs are merged. For new features,
the JIRA should have a sufficiently comprehensive description and/or links
to documentation that can be used to compile release notes.

Vlad, please add link to APEXCORE-685 so that it goes into next batch of
updates.



On Thu, Mar 30, 2017 at 7:05 AM, Vlad Rozov <v.rozov@datatorrent.com> wrote:

> I'd suggest to update contributor guideline to include that it is
> contributor responsibility
>
> 1. To assign bug to him/herself prior to starting work on a JIRA (already
> there)
> 2. If bug is already assigned and in progress, send a courtesy e-mail to
> the assigner and check the status.
> 3. Confirm type, priority and other JIRA fields. In many cases default
> values are not the best one.
>
> Committer responsibility
> 1. Resolve the JIRA with proper resolution
> 2. Verify that other JIRA fields (type, priority, assignee) are correct
>
> Please remove [VOTE] from the subject line if not voting on the release.
>
> Thank you,
>
> Vlad
>
> //On 3/29/17 23:09, AJAY GUPTA wrote:
>
>> In the release notes, the S3 Line by line module was in Bug. Should have
>> been in new feature. I have updated the JIRA type to new feature.
>>
>> On Thu, Mar 30, 2017 at 9:49 AM, Pramod Immaneni <pramod@datatorrent.com>
>> wrote:
>>
>> +1 binding
>>>
>>> Verified file and builder integrity.
>>> Verified licenses.
>>> Built source package successfully
>>> Launched and ran pi demo successfully.
>>>
>>> Thanks
>>>
>>> On Mon, Mar 27, 2017 at 11:53 PM, Thomas Weise <thw@apache.org> wrote:
>>>
>>> Dear Community,
>>>>
>>>> Please vote on the following Apache Apex Malhar 3.7.0 release candidate.
>>>>
>>>> This is a source release with binary artifacts published to Maven.
>>>>
>>>> This release is based on Apex Core 3.4 and resolves 69 issues.
>>>>
>>>> List of all issues fixed:
>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>>>> version=12338771&projectId=12318824
>>>> User documentation: http://apex.apache.org/docs/malhar-3.7/
>>>>
>>>> Staging directory:
>>>> https://dist.apache.org/repos/dist/dev/apex/apache-apex-
>>>>
>>> malhar-3.7.0-RC1/
>>>
>>>> Source zip:
>>>> https://dist.apache.org/repos/dist/dev/apex/apache-apex-
>>>> malhar-3.7.0-RC1/apache-apex-malhar-3.7.0-source-release.zip
>>>> Source tar.gz:
>>>> https://dist.apache.org/repos/dist/dev/apex/apache-apex-
>>>> malhar-3.7.0-RC1/apache-apex-malhar-3.7.0-source-release.tar.gz
>>>> Maven staging repository:
>>>> https://repository.apache.org/content/repositories/orgapacheapex-1022/
>>>>
>>>> Git source:
>>>> https://git-wip-us.apache.org/repos/asf?p=apex-malhar.git;a=
>>>> commit;h=refs/tags/v3.7.0-RC1
>>>>   (commit: 207b373f2f828636a03294bb388a279d03c5593b)
>>>>
>>>> PGP key:
>>>> http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=thw@apache.org
>>>> KEYS file:
>>>> https://dist.apache.org/repos/dist/release/apex/KEYS
>>>>
>>>> More information at:
>>>> http://apex.apache.org
>>>>
>>>> Please try the release and vote; vote will be open for at least 72
>>>> hours.
>>>>
>>>> [ ] +1 approve (and what verification was done)
>>>> [ ] -1 disapprove (and reason why)
>>>>
>>>> http://www.apache.org/foundation/voting.html
>>>>
>>>> How to verify release candidate:
>>>>
>>>> http://apex.apache.org/verification.html
>>>>
>>>> Thanks,
>>>> Thomas
>>>>
>>>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message