Language independent effective date field

At least from these commits 
http://sourceforge.net/p/archetypes/mailman/message/10519074/
http://sourceforge.net/p/archetypes/mailman/message/9458608/
the effectiveDate has been set as language independent, so this design
decision is at least 10 years old.

I'm wondering though why this was done as such because right now with Plone
and LinguaPlone I get the following behaviour:
1. Create a page -- doc1
2. Create a translation of it -- doc1-es
3. Publish doc1 and now doc1-es will get the effective date of doc1 even
though it isn't published
4. Publish doc1-es and now doc1 will get the effective date of doc1-es
because the field is languageIndependent

I find this behaviour incorrect, where it would make more sense for the
effectiveDate to not be language independent.
Consider this situation: 
1. I create a doc
2. I create a translation
3. A year later I decide to add a new language to the site and as such I add
a new translation
4. Now I publish this last translation and all of the sudden the year old
doc and it's previous translation gets their publish date modified.
5. I go to fix the publish date of the original doc back to it's publish
date, and then I mess up again the dates of the other translations.

I tried to find information of the current design decision but I couldn't
find any looking at the history or browsing through the old tickets so if
anybody remembers than do please comment on this issue.




--
View this message in context: http://plone.293351.n2.nabble.com/Language-independent-effective-date-field-tp7570904.html
Sent from the Core Developers mailing list archive at Nabble.com.

------------------------------------------------------------------------------