47.n4.nabble.com/FlexJS-Release-cycles-tp61159p61194.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
ixes.
Thanks,
Olaf
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Release-cycles-tp61159p61180.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
minor
releases which maybe contain just bug fixes.
Thanks,
Olaf
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Release-cycles-tp61159p61180.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Especially doing them with maven (
Chris
Am 18.04.17, 00:54 schrieb "Justin Mclean" :
Hi,
There are also several unresolved licensing issues, which from memory are:
- outstanding issues from the last two releases
- JSON license “do no evil” dependancy issue
- possible IP
Hi,
There are also several unresolved licensing issues, which from memory are:
- outstanding issues from the last two releases
- JSON license “do no evil” dependancy issue
- possible IP issue (MD5 code) checked in a few weeks ago
Having shorter release cycles IMO would mean it's a lot less work t
On 4/17/17, 11:34 AM, "OK" wrote:
>Hi,
>I don't know how much effort it is to cut a release but I wonder if it
>makes
>sense to increase the FlexJS release cycles to make changes much more
>transparent and to don't overload a release with too much bug
Hi,
I don't know how much effort it is to cut a release but I wonder if it makes
sense to increase the FlexJS release cycles to make changes much more
transparent and to don't overload a release with too much bug fixes and new
features.
Thanks,
Olaf
--
View this message in cont
