On 26/06/18 13:47, Emilian Bold wrote:
I think this further proves it's a bad idea to have multiple mailing lists. We
aren't even capable of having a discussion involving the whole community!
Good point!
[...]
But the Apache move is not a small thing and NetCAT should also adapt. If
any
One of the really nice features of NB has been the fact that you can run
dozens of versions installed in parallel (I usually only have not more than
four).
I grew accustomed to living on the nightly builds and, fortunately, if one
doesn't work you run "uninstall" and wait a couple of days and try
Hi all,
I like the overall concept - just some small things.
1. Having people wait for critical bugfixes for 6 months is quite long -
can we do better?
2. Do we plan to do update releases, e.g. 9.1, or 9.0 patch 1 (as before)
with just some cherrypicked stuff onto the existing release base bran
Hi all,
I created a PR with the cherry-picked commit for release90 branch.
https://github.com/apache/incubator-netbeans/pull/608
-Sven
P.S. I think we need to work on the blue color etc. in the lower half of
the updater as well... any ideas?
On Tue, 26 Jun 2018 at 13:34, John McDonnell wrote:
>
> Might every 3 months be pushing it a little?
>
> We'll constantly be in a state of picking fixes for release -> testing ->
> fixing -> release -> picking fixes for release, etc..
>
> Something like 6 months is a little more relaxed as it giv
In the mean time, I went through the 16 critical issues and there is at
least one comment to them by someone who has review them and either could
not reproduce them or couldn't do anything about them because e.g. it was a
problem with a plugin. So, I 'm not sure how we could proceed. I tried a
coup
Yeah!
-Sven
Geertjan Wielenga schrieb am
Di., 26. Juni 2018, 15:54:
> Fantastic!
>
> Thanks everyone who worked hard behind the scenes on this.
>
> Gj
>
>
> On Tuesday, June 26, 2018, Junichi Yamamoto wrote:
>
> > Great!
> > https://github.com/apache/incubator-netbeans/tree/2ndDonation
> >
> >
Fantastic!
Thanks everyone who worked hard behind the scenes on this.
Gj
On Tuesday, June 26, 2018, Junichi Yamamoto wrote:
> Great!
> https://github.com/apache/incubator-netbeans/tree/2ndDonation
>
> Thanks,
> Junichi
> On Tue, Jun 26, 2018 at 9:02 PM Geertjan Wielenga
> wrote:
> >
> > Hi a
Great!
https://github.com/apache/incubator-netbeans/tree/2ndDonation
Thanks,
Junichi
On Tue, Jun 26, 2018 at 9:02 PM Geertjan Wielenga
wrote:
>
> Hi all,
>
> On the Oracle side, we've been trying to push the 2nd donation today.
>
> We need an 'orphan' branch since that's what we need to work with
On 06/26/2018 06:47 AM, Emilian Bold wrote:
>> I think this discussion should take place on the NetCAT mailing
>> list only -- and personally I'm not sure that it is the most urgent
>> discussion at this point.
>
> I think this further proves it's a bad idea to have multiple mailing
> lists. We ar
Might every 3 months be pushing it a little?
We'll constantly be in a state of picking fixes for release -> testing ->
fixing -> release -> picking fixes for release, etc..
Something like 6 months is a little more relaxed as it gives us about 4
months between releases to make changes, introduce
Maybe you have to merge that orphan branch with master before doing a push?
--emi
‐‐‐ Original Message ‐‐‐
On 26 June 2018 3:02 PM, Geertjan Wielenga
wrote:
> Hi all,
>
> On the Oracle side, we've been trying to push the 2nd donation today.
>
> We need an 'orphan' branch since that'
Hi all,
On the Oracle side, we've been trying to push the 2nd donation today.
We need an 'orphan' branch since that's what we need to work with Emilian's
history, as I understand it.
We've tried pushing to Git and failed thus far and are discussing with
Apache infra what to do next. Only via Git
> I think this discussion should take place on the NetCAT mailing list only
> -- and personally I'm not sure that it is the most urgent discussion at
> this point.
I think this further proves it's a bad idea to have multiple mailing lists. We
aren't even capable of having a discussion involving t
Every 3 months sounds good.
--emi
‐‐‐ Original Message ‐‐‐
On 26 June 2018 11:38 AM, Neil C Smith wrote:
> On Tue, 26 Jun 2018 at 09:12, John McDonnell mcdonnell.j...@gmail.com wrote:
>
> > Secondly, what is our release cadence? Are we planning every 6 months,
> >
> > maybe attempt t
Hi,
On Mon, Jun 25, 2018 at 11:13 PM Sven Reimers wrote:
> ...3. How about ensuring that NetCAT has a representative as part of the
> (i/P)PMC - then those people can just vote -1 on a release and we do not
> need any other additional means
Note that release votes are majority votes, as per
On Tue, 26 Jun 2018 at 09:12, John McDonnell wrote:
> Secondly, what is our release cadence? Are we planning every 6 months,
> maybe attempt to keep some alignment with the JDK release cycle, or
> something longer term, like 12 months?
Thanks for kicking this off. Personally, while I'd be happy
On Mon, Jun 25, 2018 at 9:54 PM, Lars Bruun-Hansen
wrote:
>
>
> I've been offline for some time so haven't been following your excellent
> progress.
>
Thanks -- and welcome back!
Gj
>
> -Lars
>
>
> On Mon, Jun 25, 2018 at 5:08 PM, Geertjan Wielenga <
> geertjan.wiele...@googlemail.com.inval
Hi All,
In this earlier thread I put forward proposal for a timeline for releases,
to encorporate NetCat testing and voting.
Day 0: dev mailing list agrees to initiate a release, - Code Branched into
specific release Branch & Jenkins updated
Day 0: NetCat Announced + Week of signups
Day 0-6: New
I've done a separate pull request for the new splash images for the
release90 branch, since I'm using the web interface for doing these changes
and I don't see a way to do cherry picking there:
https://github.com/apache/incubator-netbeans/pull/605
Gj
On Tue, Jun 26, 2018 at 6:25 AM, Thilina Rana
I think this discussion should take place on the NetCAT mailing list only
-- and personally I'm not sure that it is the most urgent discussion at
this point.
Having a dedicated community focused on testing has always been a good
thing -- whatever we do, we mustn't lose those dedicated people who h
21 matches
Mail list logo
