Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cross-project-issues-dev] Simultaneous Release Participation

Hey Folks.

I've tried to capture the new opt-in process. I appreciate your input (and will take this opportunity to remind you that it is a wiki).

I've changed the header which adversely impacts existing links (I've decided to leave it as a cautionary tale).

The gist of it is that the Planning Council decided that if you intend to continue to participate in the simultaneous release, you need to "touch" your aggrcon file at least once between the start of the development cycle and the milestone 2 date.

No formal announcement of your participation on this list is required.

FWIW, AFAICT the following aggrcon files have not been changed in master for at least one year. 
  • PMF.aggrcon
  • XWT.aggrcon
  • actf.aggrcon
  • birt.aggrcon
  • emfstore.aggrcon
  • emft-mwe.aggrcon
  • epp-logging.aggrcon
  • jwt.aggrcon
  • m2t-xpand.aggrcon
  • usssdk.aggrcon
There's nothing wrong with a project being stable; but we still need to know that you're paying attention.

If your project is dropping off, then please pay the community the courtesy of letting them know and please push a commit to remove your project's aggrcon file from the repository.

If your project is planning to contribute new content, then you'll need to engage in the release process. There's a note in the updated text that describes a change in process that you might want to take advantage of.


Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

Back to the top