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 <johndam...@apache.org> 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 > > <geertjan.wiele...@googlemail.com> 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 > > > > >
