Thanks for the links! I've started reading the linked threads, but it'll
take some time before I finish.
I have an idea of how you do it currently, and now that I realized this
time you've tried a new thing to see if it'll work better, I'm looking
forward to seeing a discussion about the results. In the mean time I'll
try to find some arguments for and against different approaches in the
archived threads.
I also think a discussion should be held whether releasing updates just
as they become available can be beneficial to NetBeans and if so,
whether it is a worthwhile goal to pursue.
My argument is that some areas of software development, especially
related to web, can be very rapid, for example, by the time a
poorly-timed submission of an improvement of some NetBeans functionality
is accepted and released, a project whose developers could benefit from
it might be over. If some form of rapid releases was available, it could
motivate developers to contribute more to NetBeans itself, which in turn
might attract more users. But that would require to clear this somehow
with ASF, if it's only for dev@ list subscribers, then a few users would
gladly use it, sure, probably myself among them, but I'm not sure if
it'll be really worth all the trouble.
15.06.2020 11:32, Neil C Smith wrote:
On Mon, 15 Jun 2020 at 09:01, Korney Czukowski <[email protected]> wrote:
On the other hand, I'm sure a lot of people would be happy with having
nightly builds. Once a module is updated and published, it's downloaded
from the Update Center, like it used to.
Doing that for dev builds again should hopefully be on the horizon.
But that would be purely for people on the dev@ list here - as a wider
mechanism I'm not sure we could do that in line with ASF release
processes.
As for how to do it, unfortunately I don't know much of the history, so
it's very possible you've already discussed it at some point, in which
case accept my apologies for bringing this up again, but what's wrong
with having a 'living' master and 'frozen' release branches?
For the history, if you want to read, there is
https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule
https://cwiki.apache.org/confluence/display/NETBEANS/Notes+and+Discussions+on+the+Release+Schedule
and the linked to mailing list threads.
We do have a living master, we don't really (except in name) have
release branches - at first there were some small differences but now
they are exactly in sync until the moment of release - master is
always what is intended for the next release, be that in 3 months or 3
days time. We did do as you mentioned prior to 11.1. The change was
to simplify the release process to make quarterly releases manageable,
and to help make sure next release always builds on previous release.
Whether we stick with that is open to debate - we said we'd review
after a full cycle (ie. now).
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
