Alexander Limi wrote:
On Thu, 20 Sep 2007 10:49:40 -0700, Steve McMahon
<[EMAIL PROTECTED]> wrote:
Rather than trying to stop changes in the PloneHelpCenter trunk, I've
copied it off to branches/1.0, which will be the repository for work
on the upcoming 1.0 release.
PloneHelpCenter/trunk is now for work on 1.5.0. Compatibility target
for 1.5 is Plone 2.5.x and Plone 3.0.x.
branches/1.0 has a compatibility target of Plone 2.1.x and 2.5.x. May
it live a short life.
If you want to do work that's for Plone 3+ only, please open a branch.
I'm not very convinced one way or the other, but would it make sense to
call trunk "2.0" and make it only support 3.0 and up? Not sure how
trivial it is to support 2.5 and 3.0 at the same time,
From a core technical perspective that should be possible.
PHC/trunk as of now is already working on both (up to a few
failing tests on 3.0 which I hope to be able to fix soon)
but there are indeed a few other things that may justify
the distinction.
In addition to what you mention below there is for instance
the change from METAL macros to viewlets, the change away from
action icons for sending/printing as well as moving them to the
end and other little nitty-gritty things that would make life
easier I guess should we split the two (e.g PHC 1.0 for
Plone 2.1 and 2.5 or a PHC 1.5 for Plone 2.5 only should we
ever need it and PHC 2.0 for Plone 3.0)
Just my 2 cents,
Raphael
and it would be
nice to get rid of some cruft and target the 2.0 release to be used on
plone.org once it moves to 3.0 — and then let PHC 1.0 be the option for
people on 2.1 and 2.5.
--Alexander Limi · http://limi.net
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers
