eclipse / gef-classic

Eclipse GEF(tm) Classic code
Eclipse Public License 2.0
21 stars 48 forks source link

GEF 3.21 Release for Eclipse 2024-09 #455

Open azoitl opened 3 weeks ago

azoitl commented 3 weeks ago

This issue is used to track and coordinate the work for the GEF Classic 3.20.0 release to be contributed to the Eclipse 2024-03 release train. It shall serve as checklist as well as template for the upcoming release.

ptziegler commented 3 weeks ago

Would it makes sense to do the contribution one or two days before Wednesday, from now on?

It's always a little risky for me when we do our contribution, because it's usually before GEF, even though we depend on it.

azoitl commented 3 weeks ago

Would it makes sense to do the contribution one or two days before Wednesday, from now on?

I'm rather open any date that helps you.

ptziegler commented 3 weeks ago

According to the wiki, GEF would be a "+1" project. If the Eclipse milestone is contributed on a Friday, we would then ideally contribute on the next Monday.

The Eclipse project has, for example a "+0" offset: they provide their bits on the first day of any given milestone or RC date. A project like EMF is "+1" meaning that they provide their bits one day after the milestone or RC date. This basically indicates that EMF "depends on" Eclipse; they use the extra time to pull down the milestone/RC bits from their dependencies and run tests before they contribute their own bits to the milestone/RC. There are "+2" and "+3" projects as well. i.e. BIRT is "+2" because it depends on a number of "+1" projects.

azoitl commented 3 weeks ago

Thx for looking up the process. When I started contributing GEF Classic to simrel I mostly just tired what worked. Should have been more carefull and read the docs. Updated the dates above accordingly. .