Hi Neil,

> On 28. 4. 2025, at 11:56, Neil C Smith <neilcsm...@apache.org> wrote:
> 
> On Mon, 28 Apr 2025 at 10:04, Martin Balin <mba...@apache.org> wrote:
>> The proposal was there from April 9th in this form, I’m glad you are now 
>> reviewing it.
> 
> I reviewed it on the 10th!
> https://lists.apache.org/thread/o49173oy24775zo0spcflbo0xx3b5o4x
> 
>> OK, this is about releasing VSNetBeans using final commit from releasexyz 
>> branch right, when VSNetBeans is in its own repo. Right?
>> Whatever is released as main NetBeans release is then included in VSNetBeans 
>> built on top of it using that commit in submodule.
> ...
>> Decoupled releases was something we could agree on. I’ve read the thread 
>> from Jan about this and must say I didn’t understand by reading it what you 
>> mean by this? Can you explain it here on e.g. current May release of 
>> NetBeans 26 how this would look like, hypothetically? It will be better than 
>> me guessing...
> 
> Decoupled releases meant you branching at the same point as the IDE
> and platform (eg. I think branching from
> https://github.com/apache/netbeans/commit/27b43e77690d92eaf5d90e23d77b4626145c4d3f

I’ve created vsnetbeans_2600 branch from commit id you have recommended. Now we 
are running decoupled release process for VSNetBeans. Fixes for LSP are welcome 
on that branch.

> ) and running your own release process, which could have been done by
> now if you wanted.  It also meant decoupling from the issue tracking,
> milestones, metadata json, etc. used for the IDE and platform
> releases.

Martin
> 
> This is what you said you wanted to do in
> https://lists.apache.org/thread/kr2w5nfqp0yc9lbldpcmpp0j17szg7tv
> 
> It did not mean piggybacking on the IDE and platform release process,
> leaving the rest of us to stabilise and release those, unless the
> VSNetBeans team is also actively contributing to that work.
> 
> As I said on the 10th (emphasis added) - "Either we have a fully
> coordinated release process of the IDE, plugin and platform each
> quarter, which brings us back to **sharing the workload properly**.
> Or we have decoupled releases, ..."
> 
> I have always been in favour of a coordinated release process for IDE,
> platform and plugin, but not if it causes tensions with your desired
> release schedule, and not if the rest of this community is always
> being left to pick up the pieces!
> 
> Best wishes,
> 
> Neil
> 
> ---------------------------------------------------------------------
> 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



Reply via email to