Jump to:

17452 Posts in 4473 Topics by 1971 members


SilverStripe Forums » Archive » Release procedures

Our old forums are still available as a read-only archive.

Moderators: martimiz, Sean, biapar, Willr, Ingo, simon_w

Page: 1 2
Go to End
Author Topic: 3716 Views
  • Sam
    679 Posts

    Re: Release procedures Link to this post

    Sometimes a site won't want to upgrade to the latest stable release of SilverStripe: despite our best efforts, a later version might break the particular site in question.

    For this reason, I think we should keep older versions listed in branches until no-one is using that release any longer.

    There were a couple of advantages to using stable / development, but they were more "nice to have"s than anything to justify the hassle of a switch.
    Perhaps, once a release goes stable, people could request tags/2.0.0 from subversion instead of branches/2.0. This would mean we could make tags/2.0.0 read-only, and not get any accidental commits.

    If people wanted to fix a critical bug in 2.0, they could explicitly request branches/2.0 from subversion.

    Can we set up tags/* to be read-only access?

Page: 1 2
Go to Top

Want to know more about the company that brought you SilverStripe? Then check out SilverStripe.com

Comments on this website? Please give feedback.