Don’t suppose some build time (when build nbm) enhancements could be made to
make it a more automated process with help in verification and publishing to
the portal site?
Maybe in one of the Netbeans-mavenutils-nbm-maven plugins?
Eric Bresie
ebre...@gmail.com (mailto:ebre...@gmail.com)
> On Ju
On 7/14/22 6:02 AM, Jiří Kovalský wrote:
Dne 14. 07. 22 v 13:15 Michael Bien napsal(a):
On 14.07.22 12:44, Neil C Smith wrote:
So we can .. use
the NB15 baseline as initial set for NB16+ as suggested by Matthias.
just an idea,
Yes. Using the previous release as the baseline set is far from
On Thu, 14 Jul 2022 at 14:02, Jiří Kovalský wrote:
> Anyway, I very much like the idea of notification button which would
> give owners of plugins supporting already released version 14 a chance
> to quickly double check that their plugins work in version 15 and then
> request official verificatio
Dne 14. 07. 22 v 13:15 Michael Bien napsal(a):
On 14.07.22 12:44, Neil C Smith wrote:
So we can .. use
the NB15 baseline as initial set for NB16+ as suggested by Matthias.
just an idea,
Yes. Using the previous release as the baseline set is far from a new
suggestion though,
well this was onl
On 14.07.22 12:44, Neil C Smith wrote:
So we can .. use
the NB15 baseline as initial set for NB16+ as suggested by Matthias.
just an idea,
Yes. Using the previous release as the baseline set is far from a new
suggestion though,
well this was only a part what i was suggesting, it was supposed
On Thu, 14 Jul 2022 at 11:05, Michael Bien wrote:
> as already mentioned in other threads about the same topic, I have the
> suspicion that many plugin maintainers don't know that they have to
> press verify after every NB release. (I do know but i forgot at least
> twice so far but thats me)
Tha
Hi,
as already mentioned in other threads about the same topic, I have the
suspicion that many plugin maintainers don't know that they have to
press verify after every NB release. (I do know but i forgot at least
twice so far but thats me)
I believe a temporary solution would be to send a no
On Wed, 13 Jul 2022 at 18:17, Matthias Bläsing
wrote:
> from my perspective all "Verification" can do is to check a plugin
> looks normal and does not immediately destroys your data. Everything
> else will not scale (and yes not doing verification at all is IMHO an
> option).
>
> What we could do
Hi,
Am Montag, dem 11.07.2022 um 14:29 +0100 schrieb Neil C Smith:
>
> The plugins redirect will be set up to point to the currently
> non-existing https://plugins.netbeans.apache.org/data/15/
>
> Please can we add that ASAP, and also make a move to verify all
> existing verified plugins on 13 f
On Tue, 12 Jul 2022 at 03:47, Jaroslav Tulach wrote:
> > The other option is we stop verifying by NetBeans version at all?
>
> The question is: how much do we trust backward compatibility of NetBeans
> releases? We do check signatures with sigtest - e.g. it shall be compatible to
> great extent. B
> The other option is we stop verifying by NetBeans version at all?
The question is: how much do we trust backward compatibility of NetBeans
releases? We do check signatures with sigtest - e.g. it shall be compatible to
great extent. Btw. I am still successfully using NBPython support from 8.1!
Hi,
I'm just setting up some of the infrastructure and redirects in
preparation for release branching next week.
The plugins redirect will be set up to point to the currently
non-existing https://plugins.netbeans.apache.org/data/15/
Please can we add that ASAP, and also make a move to verify all
12 matches
Mail list logo
