Re: About to harmonize the version policy in /documentation
Veda Williams <veda-PRw/[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.documentation |
|---|---|
| Message-ID | <C58FFB15.D3E6%[email protected]> |
Regarding the scripting part of this, we should sniff out docs that are not in one of these categories so we can reflag them for the proper version. I'm sure you've considered that, but wanted to point it out anyways. - Veda On 1/11/09 7:23 PM, "Alexander Limi" <limi-z4DKO/[email protected]> wrote: > Hi, We recently fixed the version policy in the Products area by changing the > list of available versions from having things like Plone 3.1.x to have the > following list instead: Plone 3 Plone 2.5 Plone 2.1 Plone 2.0 Plone 1.0 The > reasoning is that if these filters are too granular, the value of them is > lost a) nobody bothers to log in and update all their version information > every time there is a minor release of Plone, and b) search suffers, since > the buckets are unpredictable because of this. In other words, we only list > what we consider "major" versions (even though that definition has changed > slightly throughout the years ;). If there is a product that only works on > (e.g.) 3.1.6 and later because of some fix, or other special circumstances, > it's the job of the author to specify this, not the filter. This particular > product would be listed as "Plone 3" compatible. I'd like to do the same > update for the documentation area, currently the list is too > granular: Plone 3.1.x Plone 3.0.x Plone 2.5.x Plone 2.1.x Plone 2.0.x The > new list would be: Plone 3 Plone 2.5 Plone 2.1 Plone 2.0 Again, if something > is so specific that it only applies to version 3.2.6 of Plone, then a) the > release manager / framework team have not done their job in respecting the > policy for what can be added, and b) the filters would quickly become > useless for search purposes anyway. If there is indeed such a difference for > documentation purposes, it should be noted in the particular document it > applies to, as you wouldn't want to maintain two different documents for > Plone 3.1.x and Plone 3.2.x anyway. Consider this a heads-up, I'll make sure > it's done in one go, scripted and ready to be used immediately when we > switch over. Complaints in a stamped, self-addressed envelope to > you-know-who. :) -- Alexander Limi · > http://limi.net ------------------------------------------------------------ > ------------------ Check out the new SourceForge.net Marketplace. It is the > best place to buy or sell services for just about anything Open > Source. http://p.sf.net/sfu/Xq1LFB ___________________________________________ > ____ Plone-docs mailing > list [email protected] https://lists.sourceforge.net/lists/list > info/plone-docs ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB