Feature #7720

Automate production of source packages for PE

Added by Nigel Kersten about 2 years ago. Updated 4 months ago.

Status:ClosedStart date:05/31/2011
Priority:NormalDue date:
Assignee:Moses Mendoza% Done:

0%

Category:-
Target version:Commercial edition - PE 2.7.1
Keywords: Affected URL:
Branch: Affected PE version:

Description

I don’t want us to be in a position where our source packages lag behind our binary releases for Puppet Enterprise.

It’s too easily a crutch for companies to hide behind while failing to fulfill their open source commitments and requirements.

I’m going to assign this to Michael to more fully specify, but it’s going to require some coordination between internal support and release management.

History

#1 Updated by Michael Stahnke about 2 years ago

I’m not certain I understand what this ticket is asking. Are we saying that we are not publishing PE sources at the same time as a PE release?

#2 Updated by Nigel Kersten about 2 years ago

Currently it’s a totally manual process, which means someone needs to remember to do it… and I’m concerned about the ramifications of untimely source publishing as an open source company.

I’d like it if we were in a position where we automatically published source packages as part of cutting a final release.

Is that a more useful description Michael?

#3 Updated by Matthaus Owens 11 months ago

  • Assignee changed from Michael Stahnke to Moses Mendoza
  • Target version set to PE Lance

We do this currently and will be looking to automate this for lance

#4 Updated by Matthaus Owens 6 months ago

  • Status changed from Accepted to Closed
  • Target version changed from PE Lance to PE 2.7.1

This is now automated as part of the enterprise-dist rakefile.

#5 Updated by Matthaus Owens 4 months ago

Released in Puppet Enterprise 2.7.1

Also available in: Atom PDF