I think the goal of the archival policy is to prevent unlimited growth of releases in the dist folder, not to impose a narrow definition of "under development". Looking at the releases available for other projects, I don't think there is any issue considering the last two release branches "under development".
Thanks On Sun, May 7, 2017 at 5:30 PM, Vlad Rozov <v.ro...@datatorrent.com> wrote: > I would consider Hadoop to be in violation of [2 < > http://www.apache.org/legal/release-policy.html#when-to-archive>]. IMO, > we don't need to violate it and should have links to the latest core and > malhar only. > > Thank you, > > Vlad > > > On 5/7/17 08:59, Pramod Immaneni wrote: > >> The policy reads we should only have "*the latest release in each branch >> that is currently under development". *That most probably means only the >> latest version for core and malhar as we are not doing active development >> on multiple branches. However, could it be loosely interpreted to include >> older release branches that are still being maintained and fixes made to? >> Hadoop, for example still has all 2.6.x and 2.7.x in svn >> https://dist.apache.org/repos/dist/release/hadoop/common/ and I mostly >> see >> maintenance fixes for the latest on those branches. Would that be >> considered a violation, if strictly going with the wording of the policy? >> >> If we wanted to keep links to even older releases, that are still in wide >> use but not being actively maintained, we could point to archives like you >> mentioned. However, I don't think we have this situation. >> >> Thanks >> >> On Fri, May 5, 2017 at 7:39 PM, Vlad Rozov <v.ro...@datatorrent.com> >> wrote: >> >> Should we limit [1 <https://dist.apache.org/repos/dist/release/apex/>] to >>> the latest core and the latest malhar according to [2 < >>> http://www.apache.org/legal/release-policy.html#when-to-archive>] and >>> point links for older releases on the download page to [3 < >>> http://archive.apache.org/dist/apex/>] according to [4 < >>> http://www.apache.org/legal/release-policy.html#how-to-archive>]? >>> >>> Unless we plan to delete release-3.2, release-3.3 and other branches, I'd >>> prefer to keep 3.2.2, 3.3.1 and other unreleased patch versions in JIRA. >>> As >>> long as those branches exist, it should be possible to see which JIRAs >>> were >>> fixed there. >>> >>> Thank you, >>> >>> Vlad >>> >>> 1. https://dist.apache.org/repos/dist/release/apex/ >>> 2. http://www.apache.org/legal/release-policy.html#when-to-archive >>> 3. http://archive.apache.org/dist/apex/ >>> 4. http://www.apache.org/legal/release-policy.html#how-to-archive >>> >>> >>> >>> On 5/5/17 08:47, Thomas Weise wrote: >>> >>> See https://github.com/apache/apex-site#updating-downloads-page >>>> >>>> added 3.6.1 >>>> >>>> Any thoughts on when to remove 3.2.2, 3.3.1 and other old patch versions >>>> in >>>> JIRA that won't see a future release? >>>> >>>> >>>> On Fri, May 5, 2017 at 7:18 AM, Vlad Rozov <v.ro...@datatorrent.com> >>>> wrote: >>>> >>>> My understanding is that it is not fully automatic and involves manual >>>> >>>>> step in updating and committing the "release.json" file and only after >>>>> that >>>>> step the download page will be regenerated. Do I miss anything? >>>>> >>>>> Any reason 3.6.1 was not added to JIRA? >>>>> >>>>> Thank you, >>>>> >>>>> Vlad >>>>> >>>>> On 5/5/17 07:09, Thomas Weise wrote: >>>>> >>>>> I removed 3.4.0 since due to change in archive file name it does not >>>>> >>>>>> match >>>>>> the download page structure. It will automatically go away when the >>>>>> download page is regenerated. >>>>>> >>>>>> >>>>>> >>>>>> On Fri, May 5, 2017 at 6:59 AM, Vlad Rozov <v.ro...@datatorrent.com> >>>>>> wrote: >>>>>> >>>>>> apex core 3.4.0 is listed on the download page and it is not part of >>>>>> >>>>>> https://dist.apache.org/repos/dist/release/apex/ >>>>>>> >>>>>>> version 3.6.1 is missing in JIRA. >>>>>>> >>>>>>> Thank you, >>>>>>> >>>>>>> Vlad >>>>>>> >>>>>>> >>>>>>> On 5/5/17 06:55, Thomas Weise wrote: >>>>>>> >>>>>>> Yes, we should keep them as otherwise they will also not be listed on >>>>>>> >>>>>>> downloads. >>>>>>>> >>>>>>>> >>>>>>>> On Fri, May 5, 2017 at 6:53 AM, Vlad Rozov <v.ro...@datatorrent.com >>>>>>>> > >>>>>>>> wrote: >>>>>>>> >>>>>>>> I removed 3.5.0 RC1 from dev. Do we need to keep apex 3.5.0 and >>>>>>>> malhar >>>>>>>> >>>>>>>> 3.5.0 and 3.6.0 in release? >>>>>>>> >>>>>>>>> Thank you, >>>>>>>>> >>>>>>>>> Vlad >>>>>>>>> >>>>>>>>> On 5/5/17 06:41, Thomas Weise wrote: >>>>>>>>> >>>>>>>>> Move of RC to release is done and new JIRA version added. >>>>>>>>> >>>>>>>>> On Fri, May 5, 2017 at 6:34 AM, Vlad Rozov < >>>>>>>>> v.ro...@datatorrent.com> >>>>>>>>> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> I'll help with moving RC candidate from dev to release. Do you >>>>>>>>>> have >>>>>>>>>> >>>>>>>>>> permission to publish artifacts to maven? >>>>>>>>>> >>>>>>>>>> Thank you, >>>>>>>>>>> >>>>>>>>>>> Vlad >>>>>>>>>>> >>>>>>>>>>> On 5/5/17 06:21, Thomas Weise wrote: >>>>>>>>>>> >>>>>>>>>>> You should be able to complete the release activities except the >>>>>>>>>>> JIRA >>>>>>>>>>> >>>>>>>>>>> version. What do you mean by "release svn repository"? >>>>>>>>>>> >>>>>>>>>>> Also, release process states that you should turn off JIRA >>>>>>>>>>>> notifications >>>>>>>>>>>> when closing issues (to not flood mailing list). >>>>>>>>>>>> >>>>>>>>>>>> Subject of closing vote should start with [RESULT] >>>>>>>>>>>> >>>>>>>>>>>> Yes, the semantic versioning check should be updated for both >>>>>>>>>>>> branches. >>>>>>>>>>>> >>>>>>>>>>>> Thomas >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Fri, May 5, 2017 at 2:34 AM, Tushar Gosavi < >>>>>>>>>>>> tus...@datatorrent.com >>>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>> As a committer, I do not have write permissions to release svn >>>>>>>>>>>> repository. >>>>>>>>>>>> >>>>>>>>>>>> Need help from PMC member to update the release repository. Any >>>>>>>>>>>> >>>>>>>>>>>> volunteers?? >>>>>>>>>>>> >>>>>>>>>>>>> Also one more clarification needed with respect to updating >>>>>>>>>>>>> semantic >>>>>>>>>>>>> versioning check. Does it needs to be done for both >>>>>>>>>>>>> release-3.6.0 >>>>>>>>>>>>> and >>>>>>>>>>>>> master branch? >>>>>>>>>>>>> >>>>>>>>>>>>> I will push the documentations after release repository is >>>>>>>>>>>>> updated. >>>>>>>>>>>>> >>>>>>>>>>>>> Thanks, >>>>>>>>>>>>> -Tushar. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Fri, May 5, 2017 at 11:35 AM, Tushar Gosavi < >>>>>>>>>>>>> tus...@datatorrent.com >>>>>>>>>>>>> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> The vote is concluded and passes. Thanks everyone for voting >>>>>>>>>>>>> and >>>>>>>>>>>>> verifying >>>>>>>>>>>>> >>>>>>>>>>>>> the release. >>>>>>>>>>>>> >>>>>>>>>>>>> binding +1 (4) >>>>>>>>>>>>> >>>>>>>>>>>>> Vlad Rozov >>>>>>>>>>>>>> Thomas Weise >>>>>>>>>>>>>> Amol Kekre >>>>>>>>>>>>>> Pramod Immaneni >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> non-binding +1 (2) >>>>>>>>>>>>>> Bhupesh Chawda >>>>>>>>>>>>>> Chaitanya Chebolu >>>>>>>>>>>>>> >>>>>>>>>>>>>> No other votes. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Will complete the release activities. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>> Tushar. >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Thu, May 4, 2017 at 12:05 PM, Chaitanya Chebolu < >>>>>>>>>>>>>> chaita...@datatorrent.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> +1 >>>>>>>>>>>>>> >>>>>>>>>>>>>> 1) Verified the file Integrity check. >>>>>>>>>>>>>> >>>>>>>>>>>>>> 2) Verified the source code using tar file. >>>>>>>>>>>>>> >>>>>>>>>>>>>>> - Extracted tar file and compiled. >>>>>>>>>>>>>>> - No binary files >>>>>>>>>>>>>>> - LICENSE, NOTICE, README, CHANGELOG.md exist. >>>>>>>>>>>>>>> - rat check >>>>>>>>>>>>>>> 3) Launched PI demo. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>>> Chaitanya >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Wed, May 3, 2017 at 7:07 AM, Pramod Immaneni < >>>>>>>>>>>>>>> pra...@datatorrent.com >>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> +1 (binding) >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> verified file integrity >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> no unexpected binary files >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> existence of README.md, NOTICE, LICENSE and CHANGELOG.md >>>>>>>>>>>>>>>> files >>>>>>>>>>>>>>>> checked build and licenses >>>>>>>>>>>>>>>> launched and ran pi demo >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Minor nitpicks >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> CHANGELOG.md has a line in the beginning of the file that >>>>>>>>>>>>>>>> has >>>>>>>>>>>>>>>> a >>>>>>>>>>>>>>>> date >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> in >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> future "Version 3.6.0 - 2017-05-04" >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Please have your key signed by some of the others in the >>>>>>>>>>>>>>> KEYS >>>>>>>>>>>>>>> >>>>>>>>>>>>>> file, >>>>>>>>>>>>>> >>>>>>>>>>>>>> right >>>>>>>>>>>>>> >>>>>>>>>>>>>>> now it is self-signed >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Thanks >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Mon, May 1, 2017 at 11:49 AM, Tushar Gosavi < >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> tus...@datatorrent.com> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Dear Community, >>>>>>>>>>>>>>> >>>>>>>>>>>>>> Please vote on the following Apache Apex Core 3.6.0 release >>>>>>>>>>>>>> >>>>>>>>>>>>>>> candidate >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> 1. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> This release adds the support for custom control tuples, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> experimental >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> support for plugins >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> and other improvements and important bug fixes. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> This is a source release with binary artifacts published to >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Maven. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> List of all issues fixed: https://s.apache.org/HQ0r >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Staging directory >>>>>>>>>>>>>>>>> https://dist.apache.org/repos/ >>>>>>>>>>>>>>>>> dist/dev/apex/apache-apex-core >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -3.6.0-RC1/ >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Source zip: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/apex/apache-apex- >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> core-3.6.0-RC1/apache-apex-core-3.6.0-source-release.zip >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Source tar.gz: >>>>>>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/apex/apache-apex- >>>>>>>>>>>>>>>>> core-3.6.0-RC1/apache-apex-cor >>>>>>>>>>>>>>>>> e-3.6.0-source-release.tar.gz >>>>>>>>>>>>>>>>> Maven staging repository: >>>>>>>>>>>>>>>>> https://repository.apache.org/content/repositories/ >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> orgapacheapex-1028 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Git source: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> https://git-wip-us.apache.org/repos/asf?p=apex-core.git;a= >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> commit;h=refs/tags/v3.6.0-RC1 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> (commit: 5a517348ae497c06150f32ce39b6915588e92510) >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> PGP key: >>>>>>>>>>>>>>>>> http://pgp.mit.edu:11371/pks/l >>>>>>>>>>>>>>>>> ookup?op=vindex&search=tushar@ >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> 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, >>>>>>>>>>>>>>>>> Tushar. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> *Chaitanya* >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Software Engineer >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> E: chaita...@datatorrent.com | Twitter: @chaithu1403 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> www.datatorrent.com | apex.apache.org >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >
