Create a meta "latest stable" distrelease

[agallou]

---

Author Name: Samuel Verschelde (@stormi) Original Redmine Issue: 210, http://mageia-app-db.tuxette.fr/issues/210 Original Date: 2011/12/12 Original Assignee: Samuel Verschelde

---

(To be used for subscriptions, selected in distrelease filter)

• add a "latest stable" distrelease * printed name: "Latest stable ($name_of_latest_release)" * in database: * ID: -1 (defined as a constant in DistreleasePeer class). If not allowed change field definition. * IS_META set to true (IS_DEVEL and IS_LATEST set to false, IS_LATEST being for actual releases) *\ NAME set to "latest" because it's what we want in the URLs
• add a "previous stable" distrelease * printed name: "Previous stable ($name_of_previous_release)" * in database: * ID: -2 * IS_META true, IS_DEVEL and IS_LATEST false *\ NAME: "previous"
• add new column IS_PREVIOUS, set to true for the actual previous stable release
• add new previous_stable_release entry in distro.yml files
• in the synchronization task, make sure to update the IS_LATEST and IS_PREVIOUS fields
• update code where we handle distreleases so that META releases are used when needed, and not used when not needed. \ filtering mechanism * + set the latest stable as default distrelease if exists * + allow latest stable and previous stable filters to be selected even when there's no actual release behind them, but show no result. \ subscription handling (form + actual notifications) ** + allow latest stable and previous stable filters to be selected even when there's no actual release behind them, because there can be in the future. * update test data since they contain a distrelease.txt file \ ...

Drawback: distros can't name their distreleases "latest" or "previous". Hopefully this will never occur, and if it occurs then we'll take care of it.

[agallou]

---

Original Redmine Comment Author Name: Samuel Verschelde (@stormi) Original Date: 2012/01/20 23:25:43 +0100

---

and also "previous stable"

[agallou]

---

Original Redmine Comment Author Name: Samuel Verschelde (@stormi) Original Date: 2012/05/07 15:57:40 +0200

---

looks like I can't force the value for the ID in the fixtures because symfony doesn't want to do that for autoincrement fields (although it's valid in SQL), so let's do without. The name + is_meta field will be sufficient.

[agallou]

---

Original Redmine Comment Author Name: Samuel Verschelde (@stormi) Original Date: 2012/05/07 21:42:28 +0200

---

Done and http://dev.madb.org and http://dev2.madb.org have been updated with it.

Now we can use those meta-releases as filters, and also as subscription criteria, such as in "notify me for every update of firefox in the latest stable release of the distribution"

For those having local madb instances, you need to:

• either do a new ./madb init (but --insert-test-data will fail for any distribution other than mageia because of a schema change, and for mageia let me a few minutes to update it)
• or apply the patches in data/upgrade/0.3 in the right order * .mysql is for mysql, .pgsql is for postgresql, .sql is for both * then ./symfony clean-propel && ./symfony propel:build-model && ./symfony propel:build-filters && ./symfony propel:build-forms

[agallou]

---

Original Redmine Comment Author Name: Samuel Verschelde (@stormi) Original Date: 2012/05/07 22:33:15 +0200

---

before ./madb init --insert-test-data, do rm tmp/data.zip to force download of the new mageia test data. For other distributions, patience, test data will be updated eventually.