Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cross-project-issues-dev] [WARNING] SimRel Headed Off the Tracks

I'm growing increasing concerned about where the Simultaneous Release train is heading:

As your elected Committer Representative, I have raised these concerns with the Eclipse Board of Directors:

But little has evolved from that to date.

I have been personally helping out everywhere I am able and I would like to help out further, e.g., with EPP, project participation, and distributing Java runtimes.  Unfortunately all my work is unfunded so I too am considering whether I'll be forced to step back from many if not most of my roles, including the participation of EMF and Oomph in the Simultaneous Release process.

How much workload is it to manage all the necessary work involved in producing the release train?  That's unclear at this point, but what's all too clear is that even seemingly simple things like getting the license text correct and providing only signed content has proven to be an exercise in herding cats.  It's simply a huge challenge just to get each cat's awareness.  The latest 2020-03 M1 has introduced yet another SUA 2.0 variant and has unsigned content:

And even when we get all these things correct, hidden problems quietly hammer the download server almost to death making for a bad installation/update experience:

In addition, it seems that the following problem might well happen yet again for the next release:

Compound all these difficult issues with a challenging migration to JIRO leaves me shaking my head.  I am wondering how many weeks of effort I personally will need to invest in order to migrate (re-implement) my existing jobs to what feels to me like crippled infrastructure.   Many projects will be faced with this same task and my general migration concerns remain open:

Poor communication, continued complacency, and lack of cohesive leadership/management seems to be heading the train off the track.  It seems to me each of us has three choices:

  1. Step forward and volunteer to do some or all this necessary work yourself.
  2. Speak to your Board representative(s) about cohesive management of this process.  Even if you don't work for a Strategic Developer member, there are six elected Board members who represent you and/or your organization:
  3. Do nothing based on the hope that the commons will function unattended.


Back to the top