[
https://issues.apache.org/jira/browse/MYFACES-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644305#comment-17644305
]
Werner Punz edited comment on MYFACES-4522 at 12/7/22 12:19 PM:
----------------------------------------------------------------
Ok I was wrong... 2.3next has a different agenda, we basically cut off a ton of
old browser support in 2.3 next.
Thing is the baseline of 2.3next is ie9 so still very old.
I would not have any problem to sync this code back into 2.3, but I cannot
decide that alone.
I just do not want to maintain another even older codebase anymore.
2.3 Next back then was founded to get rid of some legacy code.
My proposal is to keep 2.3next and 2.3 in sync regarding the js codebase for
now, but increase the baseline for the supported browsers for 2.3 to ie9!
[~tandraschko] and [~volosied] please comment on this whether we can do it or
stick with the older 2.3 codebase which carries aroound way more legacy code
than 2.3-next!
Another option would be just to roll in the most importand and non intrusive
fixes into 2.3 and for more support on certain issues or fixes, push the users
towards the next codebase.
I would prefer the keep in sync solution however... because not doing it means
I have to support 4 codebases
2.3, next, master and the typescript version, this is cumbersome and error
prone!
was (Author: werpu):
Ok I was wrong... 2.3next has a different agenda, we basically cut off a ton of
old browser support in 2.3 next.
Thing is the baseline of 2.3next is ie9 so still very old.
I would not have any problem to sync this code back into 2.3, but I cannot
decide that alone.
I just do not want to maintain another even older codebase anymore.
2.3 Next back then was founded to get rid of some legacy code.
My proposal is to keep 2.3next and 2.3 in sync regarding the js codebase for
now, but increase the baseline for the supported browsers for 2.3 to ie9!
[~tandraschko] and [~volosied] please comment on this whether we can do it or
stick with the older 2.3 codebase which carries aroound way more legacy code
than 2.3-next!
> jsf.js sync the 2.3-next files back into 2.3
> --------------------------------------------
>
> Key: MYFACES-4522
> URL: https://issues.apache.org/jira/browse/MYFACES-4522
> Project: MyFaces Core
> Issue Type: Task
> Affects Versions: 2.3.10
> Reporter: Werner Punz
> Assignee: Werner Punz
> Priority: Major
>
> We have had a ton of fixes in the old codebase which made it so far into
> 2.3-next and 4.0
> however given that 2.3 still is in active development we should sync those
> changes back into the 2.3 branch. Given 2.3-next and 2.3 share the same code
> on JS level, a simple diff should suffice instead of cherry picking every fix.
> I will make a single commit under this issue for 2.3
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
