I think one thing we should do that I don't remember doing is keeping close track of issues such as this one:
https://issues.apache.org/jira/browse/NETBEANS-4950 If I had been aware of it, I would have pushed for that fix to have gone into nb-javac, maybe that can still be done, i.e., we produce a new nb-javac? We need to keep track at least of these issues marked critical -- and we need to try to involve those reporters in assisting in verifying that fixes for the issues they report work for them. Gj On Thu, Mar 11, 2021 at 3:05 PM Neil C Smith <[email protected]> wrote: > On Thu, 11 Mar 2021 at 13:18, Geertjan Wielenga <[email protected]> > wrote: > > Now that every 12.3 bit and byte (knock on wood) is out the door, let's > > immediately list all our grips and gripes. > > > > What worked well, what didn't, what should be repeated, and what should > > never be done again? > > All I'm going to say is that having two release managers has worked > really well. And thanks for that! :-) > > Of course, with two there's always the potential for a little overlap. > ;-) I was just planning a similar-ish thread to discuss "making > quarterly releases more manageable". I have a few thoughts / > proposals there, some of which the two of us talked about already, but > I'll leave that for a few days as this discussion might change that > one. > > 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 > > > >
