Michael Jouravlev wrote:
SAF1 could have future if migration to SAF2 were impossible or too
complicated. But according to your plan, migration from SAF1 to SAF2
should take days. What is the point of keeping Action 1.x "to be
developed actively"?
I am not objecting, I am just asking. Trying to understand where I am ;-)
It is more a question of committer time and energy. There are committers that
want to only work with Action 1, so even if there is a smooth upgrade path,
Action 1 will continue to be developed.
Now, there is a difference between actively developed and simply supported. The
Struts PMC is totally committed to support Action 1, meaning bug fixes, security
fixes, etc. Whether Action 1 sees more releases with fancy new features is up
to those that want to do the work.
Personally, I'll be supporting Action 1, but actively developing 2. If Action 1
keeps going, I might backport some things to it, however, to make the conceptual
transition for the developer easier to 2.
Don
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
