Hi,
Today I consider it closed and proposal for VSNetBeans own repo approved 
https://cwiki.apache.org/confluence/display/NETBEANS/VSNetBeans+Repository+and+Updated+Releases
I will start working on getting the repository under Apache umbrella on GitHub.
Martin

> On 23. 4. 2025, at 12:00, Martin Balin <mba...@apache.org> wrote:
> 
> 
> 
>> On 23. 4. 2025, at 10:26, Neil C Smith <neilcsm...@apache.org> wrote:
>> 
>> On Wed, 23 Apr 2025 at 08:01, Martin Balin <mba...@apache.org> wrote:
>>> We have consensus to separate VSNetBeans code as specified in proposal ... 
>>> I will release VSNetBeans 26.0.0 from netbeans repo “release260” branch 
>>> after VOTE on NetBeans 26.0 is complete. It will be release of 
>>> complimentary artifact done from the same source as main release.
>> 
>> I'm curious how you read my previous email as leading to consensus on
>> this?!  I am -1 on this idea.  Either we have decoupled release
>> processes with basic coordination only on branch points from master,
>> or we have a fully integrated release process of all artefacts with
>> properly shared workload and everyone taking responsibility for
>> everything we release.
> Hi
> No problem on releasing next VSNetBeans when it will be separated exactly as 
> written in 
> https://cwiki.apache.org/confluence/display/NETBEANS/VSNetBeans+Repository+and+Updated+Releases
> 
> “hybrid” mode was meant just to have continuum in VSNetBeans  releases after 
> main IDE releases, lets not do it. Timing on how long it will take to get 
> netbeans-vscode repo is to be known… 
> Hope this helps
> Martin
> 
> 
>> 
>> Neil
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org 
>> <mailto:dev-unsubscr...@netbeans.apache.org>
>> For additional commands, e-mail: dev-h...@netbeans.apache.org 
>> <mailto:dev-h...@netbeans.apache.org>
>> 
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Reply via email to