Hi Steve,

Steve McMahon schrieb:
Here's a draft for a public policy statement. I invite feedback and
wordsmithing.

Thanks for writing the draft. I've only 2 comments.

1. I saw different working names for the policy and I think it should be something obvious like "Plone [Version] Support Policy" or "Plone Lifecycle Support Policy".

2. A table with the current/future versions would help. It's not really part of the policy, but a table helps to understand it and gives an idea how long the support cycles are.

                                 (supposable)
                Series           Release Date
            2.5    3.x    4.x
Release
2.5          M      -      -      Sep 2006

3.0          M      M      -      Aug 2007

3.1          S      M      -      May 2008

4.0         EOL     M      M      2010 or 2011 (???)

4.1         EOL     S      M      undecided

M = Active Maintenance (development, bug fixes, and refinement)
S = Active security support (security fixes)
EOL = End of Life, especially no more Security fixes


..Carsten


"""
The Plone project offers differing levels of support for non-current
versions of Plone.

Active maintenance of Plone happens for one major version of Plone at a time.
Once a new major version is released, the old major version is
maintained until the first minor version of the new major version is
released. Active maintenance includes development, bug fixes, and
refinement.

Active security support happens for the latest two major Plone
versions at all times. However, there may be security-related fixes
that are practical for the current version of Plone, but are not
practical for earlier versions. This may be the case if the fix to an
earlier version would require widespread or structural changes.

Plone 2.5, 3.x and 4.x are considered major versions of Plone. Plone
3.1, 3.2, 3.3, 4.1, 4.2 are considered minor versions of Plone.


Please note that this is not a guarantee that any particular bug will
be fixed or development undertaken. Plone is an open-source software
project developed collaboratively by hundreds of persons from around
the world, and progress depends on the interest and skill of those
developers. As with any project, your best guide is probably the work
done in the past. We believe the record of the Plone project on this
score is excellent and invite your scrutiny and suggestions.
"""



On Tue, Apr 21, 2009 at 11:36 AM, Wichert Akkerman <wich...@wiggy.net> wrote:
Previously Steve McMahon wrote:
Unless anyone can make a case for re-evaluation, I hope we can take a
common line on this in discussions in the other lists. In particular,
we should be careful in any statement that Plone 2.5.x is unsupported
to make sure that this only refers to active maintenance and not to
security support.
Just as important: we should communicate this policy clearly. I suggest
a post to plone-announce describing this policy and an easily findable
document on plone.org (preferably reachable in 2 or 3 clicks from the
frontpage).

Wichert.

--
Wichert Akkerman <wich...@wiggy.net>    It is simple to make things.
http://www.wiggy.net/                   It is hard to make things simple.






_______________________________________________
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team

Reply via email to