Forum Discussion

Alfred_Heijkoop's avatar
Alfred_Heijkoop
Icon for Contributor III rankContributor III
6 months ago

Release notes for Agents

The versions of the agents are more or less independent from the SL1 releases. This is giving the flexibility to release and install agents in faster cycle.  By making it a independent software comp...
agent
  • ErickBurgess's avatar
    ErickBurgess
    3 months ago

    The SL1 Agent doesn't have it's own Release Notes because we do not formally release it outside of SL1 releases.  We do occasionally provide a new version of the agent during support cases to fix the reported issue.  This is similar drop file provided during support cases to fix an SL1 issue.

    Publishing Release Notes would require a method to release and install that agents.  This isn't a problem for Gen3 Agent users as the container including the agent packages are published to Harbor.  It is a problem for Gen1 Agent users as there isn't a way to install the agent packages outside of SL1 upgrades.

    I'll discuss with Release Management and Documentation teams.

    Regards,

    Erick

ErickBurgess's avatar
ErickBurgess
Icon for Moderator rankModerator

The SL1 Agent doesn't have it's own Release Notes because we do not formally release it outside of SL1 releases.  We do occasionally provide a new version of the agent during support cases to fix the reported issue.  This is similar drop file provided during support cases to fix an SL1 issue.

Publishing Release Notes would require a method to release and install that agents.  This isn't a problem for Gen3 Agent users as the container including the agent packages are published to Harbor.  It is a problem for Gen1 Agent users as there isn't a way to install the agent packages outside of SL1 upgrades.

I'll discuss with Release Management and Documentation teams.

Regards,

Erick

Alfred_Heijkoop's avatar
Alfred_Heijkoop
Icon for Contributor III rankContributor III
3 months ago

Hi Eric,

Thanks a lot. 

From best practices, I think it should good to follow a certain release process. 
From customer end we now what is delivered (and what not) and how to install. From engineering, SRE and Support prospective you might want to know as well what is fixed in which version so you can apply forward fixes on those to the next branch.
No surprises anymore in your QA cycle!

If needed, you can always include me in discussion-meeting.

Looking forward to your response.

Alfred Heijkoop