Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Piwik.org should handle two types of release: STABLE and BETA releases. #725

Closed
mattab opened this issue May 16, 2009 · 4 comments
Closed

Piwik.org should handle two types of release: STABLE and BETA releases. #725

mattab opened this issue May 16, 2009 · 4 comments
Labels
c: Website matomo.org For issues related to our matomo.org website. Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Milestone
0.4

Comments

@mattab
Copy link
Member

mattab commented May 16, 2009

Even though Piwik is not stable as such, some releases are more risky than others (eg. 0.2.35). In this case we should have released under a "beta" label.

Currently the release script builds from a SVN tag. It checkouts the tag, delete some useless directories (tests/ etc.), and then packages up, copies into http://builds.piwik.org, and updates the http://builds.piwik.org/LATEST with the version number.

Instead we should have two releases (or event three?).

  • the current official release (near stable)
  • a beta release (if the version name contains "rc" or "beta" ?)
  • a nightly build of the SVN trunk

The release could be automatically flagged as beta if the name contains beta or RC. It would not update http://builds.piwik.org/LATEST (this file is used by all Piwik installs to check what is the latest piwik release and print an "You need to update" message).

The beta could be advertised below the red download box on Piwik.org: "Download 0.2.37" and below "Download and test the beta release: 0.4rc1"
@mattab
Copy link
Member Author

mattab commented May 18, 2009

we have to release 0.4 with the beta label, and keep providing 0.2.X as stable alternative.

@robocoder
Copy link
Contributor

Reminder to create a 0.2 maintenance branch in svn.

@mattab
Copy link
Member Author

mattab commented May 18, 2009

vipsoft, I don't think we need a branch. In the rare probability case where we need to fix a security issue in 0.2.x then we would just backport the fix to a fresh checkout of the last 0.2.x tag, fix it and tag it in 0.2.x+1. SVN Tags are enough for us, I see branches as more useful when you know there will be many changes in parallel.

@mattab
Copy link
Member Author

mattab commented Jun 2, 2009

it is done, you can see the latest alpha/dev/beta/rc (any tag matching these strings) will be updated in http://builds.piwik.org/LATEST_BETA

I just don't know where to advertise this on the website at this stage, so will just not advertise it. We might want to create a "Downloads" page on piwik.org/download/ and list the two releases availables + links to the older builds. any suggestion?

@mattab mattab added this to the Piwik 0.4 milestone Jul 8, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
c: Website matomo.org For issues related to our matomo.org website. Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Projects
None yet
Milestone
0.4
Development

No branches or pull requests
2 participants
@mattab @robocoder