Guys,
As you know, 3.0 and 3.0.1 have been released. We now have a more
stable codebase and product than before these releases. Therefore, I
think it would make sense to be very careful with dependencies. I
would even say "conservative" rather than "careful". So I would like
to ask you the following:
* avoid updating dependencies between minor releases. (i.e hold on
until Magnolia 3.1 for instance)
* avoid updating dependencies silently. (let's mention it or
discuss it on the list)
* avoid updating dependencies without reporting it on jira.
* if the dependency update is critical (i.e it fixes Magnolia
bugs), then let's update it, but it's important to be aware of all
the impacts this could have.
Of course, we understand that everybody has his projects running on
Magnolia, and sometimes, it is more urgent for one or another to
update such and such dependencies. Never forget that we are
developing a product, though; which means, basically, that any change
in the product will impact several projects. Since minor releases are
supposed to be transparent to update to, it's probably best to avoid
such changes. (and I suppose it's always possible to update the
dependency on your local projects if needed)
Do you guys think it's time for branching ? (i.e branch for 3.0.x bug
fixing) Do you think the release has been out long enough to consider
it stable enough that we can now focus on larger tasks ?
On a related note, I would like to ask everyone to report any code
change in Jira. It's very important that we can rely on Jira for
change logs. Since we now have released, we can't afford to be unsure
of what changed between two versions.
Lastly, I wouldn't want this mail to sound like an attack to anyone;
you know we value your work. I just want to ensure some quality and
stability: we can't afford to work in the same unstructured way as
before the 3.0 release anymore. Could I ask everyone involved to
report the appropriate changes on Jira ?
Thanks a lot,
greg
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------