Re: [DISCUSS] Apache NetBeans Incubator Proposal
On 9/17/16, 8:54 AM, "Jochen Theodorou" wrote: >On 17.09.2016 10:23, Geertjan Wielenga wrote: >> Nightly builds is all that's needed, indeed, no one needs to announce >>them, >> they should simply be available. Agreed it's important to distinguish >> between nightly builds and official releases, that's exactly how >>NetBeans >> works currently. The #1 requirement here is that there should be nightly >> builds and that is supported, from your response here. > >may I ask for whom and what the nightly builds are in your case? If it >is for developers only there should be no problem. Where "developers" is the folks contributing to the code in Apache, not users of the code. IIRC, there are also restrictions on how folks find out about the "nightly" builds. It can't be listed in the release info on the web site, for example. -Alex - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] MADlib v1.9.1-rc2
On Tue, Sep 6, 2016 at 9:39 PM, Frank McQuillan wrote: > > Hello Incubator PMC, > > The Apache MADlib (incubating) community has voted on and approved the > proposal to release MADlib v1.9.1-rc2. > > The voting result is available at: > https://mail-archives.apache.org/mod_mbox/incubator-madlib-dev/201609.mbox/%3CCAKBQfzT0pw1%3DP-KWuZVsAwORdHdz792WvUtR-DbM%2BH8EkiZdSA%40mail.gmail.com%3E > > This is the 3rd release for Apache MADlib (incubating). > > The main goals of this release are: > * new modules (1-class SVM for novelty detection, prediction metrics, > sessionization, pivoting) > * improvements to existing modules (class weights in SVM, overlapping > patterns in path) > * performance improvements (path) > * platform updates (PostgreSQL 9.5 and 9.6) > * bug fixes > * doc improvements > > For more information including release notes, please see: > https://cwiki.apache.org/confluence/display/MADLIB/MADlib+1.9.1 > > To run check RAT, please do: > > $mvn verify > > first to get the correct RAT output. Look inside of pom.xml to see the > classes of exceptions we're managing there for RAT. > > We're voting on the source (tag): > rc/1.9.1-rc2 > > Source Files: > https://dist.apache.org/repos/dist/dev/incubator/madlib/1.9.1-incubating-rc2 > > Commit to be voted upon: > https://git-wip-us.apache.org/repos/asf?p=incubator-madlib.git;a=commit;h=e1c99c1538dc124c9b323ba76382ba2af05c6892 > > KEYS file containing PGP Keys we use to sign the release: > https://dist.apache.org/repos/dist/dev/incubator/madlib/KEYS > > Please vote: > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) +1 (binding) I checked: * imported keys from the provided KEYS file * checksums and signatures * the release archive is identical to the content of the tag * DICLAIMER, LICENSE and NOTICE are all as they should be * ran RAT check (via mvn verify) and made sure that the license headers in files get properly recognized and the excluded BSD licensed files are correctly excluded * all brand new files in this release have ALv2 headers Minor nits that I stills strongly suggest you address in future release: * name of the top level folder in the archive is weird. The usual practice is to call the top level folder as - Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Apache NetBeans Incubator Proposal
On Sat, Sep 17, 2016 at 10:54 AM, Geertjan Wielenga wrote: > Hi all, > > Can we be specific about what info is needed, or what further details > specifically, before going into a vote for acceptance of the proposal? My > concern is that each question we answer is answered by further questions to > answer. Maybe we could do a phone conference with the NetBeans > infrastructure side together with the Apache infrastructure side. Maybe we > can work through the infrastructure challenges during incubation. > My concern is this - I don't want to end up in a situation where we are surprised by what the project actually needs. The ASF's infrastructure budget is pretty small all things considered, and I want both sides to understand what's needed and expected before we decide that the marriage is perfect. I don't want the Foundation to assume a responsibility that we can't reasonably fulfill, and I don't want to deleteriously affect the NetBeans community because of those limitations. I don't see a lot of downside in exploring what the NetBeans community actually needs and those costs and whether or not the ASF can meet those needs. Daniel Gruno is Infra's representative, and he owes me (and the IPMC, and the rest of Infra) a report on what your needs are, and what the costs are to provide them. I'll admit that we don't normally go to this level of effort for a potential podling, but it's not that frequent that we have a potential podling with 20 years of history or of the size of NetBeans either. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Apache NetBeans Incubator Proposal
On 17.09.2016 10:23, Geertjan Wielenga wrote: Nightly builds is all that's needed, indeed, no one needs to announce them, they should simply be available. Agreed it's important to distinguish between nightly builds and official releases, that's exactly how NetBeans works currently. The #1 requirement here is that there should be nightly builds and that is supported, from your response here. may I ask for whom and what the nightly builds are in your case? If it is for developers only there should be no problem. bye Jochen - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Apache NetBeans Incubator Proposal
On Sat, Sep 17, 2016 at 11:14 AM Bertrand Delacretaz wrote: > Hi, > > On Sat, Sep 17, 2016 at 4:54 PM, Geertjan Wielenga > wrote: > > ...Can we be specific about what info is needed, or what further details > > specifically, before going into a vote for acceptance of the proposal?... > > Unless I missed something I see only David Nalley, speaking has VP > infra, who has requested that we wait before voting in order to > clarify the infra requirements. > > I understand the NetBeans team is working with Daniel Gruno to clarify > those, and will report here with the results so we'll wait until we > have Daniel and/or David's ok to proceed. > Agreed. For what its worth, I think from an incubator standpoint we are good to move forward to a vote. This has gotten a lot of input, though realistically 7 days is a good amount of time to allow for a discussion. I can understand with everything going on in the community in the next 7 days why this is critical. I'll be happy to be able to say I voted +1 on this while at JavaOne next week. John > > If people have other questions that need to be addressed before > voting, please let us know, and if needed we can add a numbered list > of these questions as an appendix to > https://wiki.apache.org/incubator/NetBeansProposal to keep track of > things in a central place. > > Also, everybody please use Precise Quoting (tm) in general so that we > can make sense of those somewhat complex discussions. > > -Bertrand > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] Apache NetBeans Incubator Proposal
On Thu, Sep 15, 2016 at 4:05 PM, Daniel Gruno wrote: > ...Seeing as no one else from that PMC chimed in, I guess I'll be the > punching bag here, Bertrand :) Count me in Looking forward to that ;-) I have added you as a mentor to https://wiki.apache.org/incubator/NetBeansProposal -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Apache NetBeans Incubator Proposal
Hi, On Sat, Sep 17, 2016 at 4:54 PM, Geertjan Wielenga wrote: > ...Can we be specific about what info is needed, or what further details > specifically, before going into a vote for acceptance of the proposal?... Unless I missed something I see only David Nalley, speaking has VP infra, who has requested that we wait before voting in order to clarify the infra requirements. I understand the NetBeans team is working with Daniel Gruno to clarify those, and will report here with the results so we'll wait until we have Daniel and/or David's ok to proceed. If people have other questions that need to be addressed before voting, please let us know, and if needed we can add a numbered list of these questions as an appendix to https://wiki.apache.org/incubator/NetBeansProposal to keep track of things in a central place. Also, everybody please use Precise Quoting (tm) in general so that we can make sense of those somewhat complex discussions. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Apache NetBeans Incubator Proposal
Hi all, Can we be specific about what info is needed, or what further details specifically, before going into a vote for acceptance of the proposal? My concern is that each question we answer is answered by further questions to answer. Maybe we could do a phone conference with the NetBeans infrastructure side together with the Apache infrastructure side. Maybe we can work through the infrastructure challenges during incubation. It is clear that the current complexities of the NetBeans Mercurial repositories is because of the specific style of working that the NetBeans team has had, while will be moved to the standard Git way of working, which will reduce the number of repositories significantly, while also standardizing the process of working with NetBeans source code via the adoption of the standard Apache way of doing so. The various different servers and VMs that NetBeans has needed have also clearly been built up over time and are not a mandatory requirement either, here too we'd like to adopt the standard Apache approach as much as possible. The hosting of the NetBeans plugins is not an immediate problem and we could solve it by asking one or more of the individual committers to request their organizations to host those plugins. Many of those plugins are old or not maintained anymore and the total number that we would want to continue making available could shrink significantly, also because NetBeans is focused far more on 'out of the box' features than on plugins. Our willingness to comply to standard structures and services provided by Apache, while having a large community that could provide services we need that Apache can't provide should give confidence that the incubation process will be a success. Thanks, Geertjan On Sat, Sep 17, 2016 at 3:23 PM, John D. Ament wrote: > Actually, I think a nightly build artifact would only be supported via > Jenkins. Travis can upload to things like nexus, but I don't believe we > publish our credentials outside of the environment. > > This may also be a use case for jenkins pipelines, to orchestrate the build > steps required programmatically via a groovy DSL instead of job configs. > > John > > On Sat, Sep 17, 2016 at 9:19 AM Bertrand Delacretaz < > bdelacre...@apache.org> > wrote: > > > On Sat, Sep 17, 2016 at 10:23 AM, Geertjan Wielenga > > wrote: > > > ...The #1 requirement here is that there should be nightly > > > builds and that is supported, from your response here... > > > > Yes, definitely, for that there's at least Jenkins at > > https://builds.apache.org/ and Travis, > > https://blogs.apache.org/infra/entry/apache_gains_additional_travis_ci > > > > -Bertrand > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > >
Re: [DISCUSS] Apache NetBeans Incubator Proposal
Actually, I think a nightly build artifact would only be supported via Jenkins. Travis can upload to things like nexus, but I don't believe we publish our credentials outside of the environment. This may also be a use case for jenkins pipelines, to orchestrate the build steps required programmatically via a groovy DSL instead of job configs. John On Sat, Sep 17, 2016 at 9:19 AM Bertrand Delacretaz wrote: > On Sat, Sep 17, 2016 at 10:23 AM, Geertjan Wielenga > wrote: > > ...The #1 requirement here is that there should be nightly > > builds and that is supported, from your response here... > > Yes, definitely, for that there's at least Jenkins at > https://builds.apache.org/ and Travis, > https://blogs.apache.org/infra/entry/apache_gains_additional_travis_ci > > -Bertrand > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] Apache NetBeans Incubator Proposal
On Sat, Sep 17, 2016 at 10:23 AM, Geertjan Wielenga wrote: > ...The #1 requirement here is that there should be nightly > builds and that is supported, from your response here... Yes, definitely, for that there's at least Jenkins at https://builds.apache.org/ and Travis, https://blogs.apache.org/infra/entry/apache_gains_additional_travis_ci -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Apache NetBeans Incubator Proposal
Nightly builds is all that's needed, indeed, no one needs to announce them, they should simply be available. Agreed it's important to distinguish between nightly builds and official releases, that's exactly how NetBeans works currently. The #1 requirement here is that there should be nightly builds and that is supported, from your response here. Geertjan On Fri, Sep 16, 2016 at 10:28 AM, Bertrand Delacretaz < bdelacre...@apache.org> wrote: > Hi, > > On Fri, Sep 16, 2016 at 7:00 AM, Geertjan Wielenga > wrote: > > ...the #1 requirement is for Apache NetBeans to be able > > to produce daily/release builds and to upload them to netbeans.org or > > another download area under Apache > > Daily releases are problematic in Apache projects as the PMC needs to > approve releases, and in general those votes last at least 72 hours > due to our async collaboration model. > > AFAIK Apache Cordova for example is making very frequent releases, it > might be interesting to find out how they enable that, in due time. > > Nightly builds should not be announced outside of the project's > developers mailing lists, to mark a clear line between those and > official releases. > > All those things can be discussed during incubation of course, just > wanted to mention them due to the above #1 requirement. > > -Bertrand > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
