Hi all,
(Regarding the splash screens: I think Laszlo is taking the lead, I just
posted some quick & dirty SVG files as a possible solution).
I agree with Matthias & Laszlo: let's improve the release process even
further before tackling patch releases.
Also let's settle down the repository & jenkins infra changes after the
"-incubator" removal.
Also let's clarify what's in our backlog. Do we want to tackle
plugins.netbeans.org? If so, before release 12? Release 14? When is the
next donation expected?
Cheers,
Antonio
El 28/04/2019 a las 8:44, Matthias Bläsing escribió:
Hi,
Am Freitag, den 26.04.2019, 22:57 -0700 schrieb Laszlo Kishalmi:
As Gradle was a new out-of-the box feature, I've received some
issues/feedback. I've already fixed some of them.
I would like to do a release of those changes. Those fixes might be not
that important, but what I'm really curious, that actually can we, and
how can we roll out such a partial patch release?
at some point in the past we said, that we wanted to do time based
releases and I would still follow that thinking.
I would branch any release of master, as late as possible, (not some
random other base), do testing and only minimal cherry-picking,
release. Repeat X months later.
That way we know:
- when a release is due
- what will be in the release (the state of master)
Greetings
Matthias
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
