Feature #2393

We should maintain a dynamically-built 'next' branch

Added by Luke Kanies almost 3 years ago. Updated over 2 years ago.

Status:Closed Start date:07/06/2009
Priority:Normal Due date:
Assignee:James Turnbull % Done:

0%
Category:installation
Target version:0.25.1
Affected Puppet version:0.24.8 Branch:
Keywords:
Votes: 0

Description

As discussed on the list, we should have a ‘next’ branch containing all of the code to be released in the next version, and that branch should be rebuilt from scratch as necessary.

History

#1
Updated by Luke Kanies almost 3 years ago

  • Status changed from Accepted to In Topic Branch Pending Review
  • Assignee changed from Luke Kanies to James Turnbull

Pushed a simple example in the tickets/master/2393 branch in my repo.

#2
Updated by James Turnbull almost 3 years ago

  • Status changed from In Topic Branch Pending Review to Code Insufficient

#3
Updated by Luke Kanies almost 3 years ago

Anything else to say on this? Hate the idea? Have you had a chance to play with it?

#4
Updated by James Turnbull over 2 years ago

  • Status changed from Code Insufficient to Accepted
  • Target version set to 0.25.1

#5
Updated by James Turnbull over 2 years ago

  • Status changed from Accepted to Closed

Modified this code (so it works now… :) ) and pushed in commit:2283605ba63b39deec30bd71b5d0879630f63e6d in branch master.

Also available in: Atom PDF