PCM Development/Palladio Concall/Minutes 20170814

Aus SDQ-Wiki

Participants

  • Amine
  • Dominik
  • Erik
  • Steffen
  • Stephan

Agenda

Please add things you want to discuss to the agenda below.

  1. Release resheduling
  2. When using the drop, features/plugins cannot be updated. Is this intended that way?
  3. How to handle deprecated code in SVN?
    • Hard for new developers to distinguish living from dead code
    • Code in Completions Addon deprecated?
  4. Improvements of JIRA workflow?
    • Replace "Open" with "Unconfirmed"?
    • Documentation of semantics of "affects version" and "fix version"?
  5. Palladio-Homepage

Minutes

  1. Release rescheduling
    • Release has been postponed (Status of EDITORS-202). (Property sheets are not supported in Sirius 5)
    • Problem: Bug in Sirius 5. Has been fixed in Nightly Build. Should be fixed in Sirius 5.0.2. Current code does not longer support with Sirius 4. Sirius 5 is available for Neon and Oxygen.
    • Should we release for Sirius 4 or 5?
      • St.S.: Sirius 5
    • Build against Nightly or release against 5.0.2?
      • St.S.: Wait and build against 5.0.2 because b3-aggregator mirrors metadata. Wait for Sirius release.
    • Current Options
      • TODO: Amine: b3 to Sirius 5, Minimum Version Constraint: 5
      • TODO: After Sirius Release: Set aggregator to Sirius 5 release.
      • If someone wants to use the property sheets, they have to update to nightly (TODO: Amine: send mail)
      • (Side note: SB did not get mail by JIRA regarding EDITORS-202)
  2. When using the drop, features/plugins cannot be updated. Is this intended that way?
    • SB: That is not the intended way and that used to work at some point.
    • TODO: Stephan: Report (detailed!) bug (i.e. find out who put that in the Wiki and let them create the Bug Report) (Wiki blame). SB -> Watcher
  3. How to handle deprecated code in SVN?
    • Hard for new developers to distinguish living from dead code (Code in Completions Addon deprecated?)
    • Move deprecated code to [1]
    • TODO: Stephan: Wiki documentation for the handling of old code.
  4. Improvements of JIRA workflow?
    • Problem: Hard to see if a bug has been confirmed or is reproducible
    • Proposed workflow: [2]
    • Add Affected Version for confirmed bugs.
    • Probably mostly sensible for bugs
    • Replace "Open" with "Unconfirmed/Confirmed"?
    • Documentation of semantics of "affects version" and "fix version"?
      • SB: The person that closes a bug puts the fix version (which ideally is the upcoming release version).
      • Affects Version is the one in which the bug was found / the feature should be implemented.
      • Fix version is the one in which the bug is fixed/feature is integrated
  5. Palladio-Homepage
    • palladio-simulator.com has been ported to new typo3. in case there are issues -> mail to Erik
    • Caroussel on the top of the page:
      • Current Release, Palladio-Book (Full Palladio experience), CloudScale-Book (Engineering cloud systems w/ Palladio),
      • TODO: Steffen: Write article for Cloud Scale book (appraisal by Ralf)
      • Text: [3]
      • -System Z, -1&1
      • Instead of case studies: "Industry-proven Analysis Approach" --> Link to case studies
      • Nachtrag: [4]
    • TODO: Erik: Include Twitter stream instead of (old) news on the right
    • Who manages the Palladio Twitter account?
      • TODO: Stephan: Contact Klaus

Next Concall

  • 11.09.2017