Well the manual effort of releasing itself isn’t that much. In case of a maven
release its executing two commands and then going to Apache’s Nexus Web UI and
doing a few clicks. It’s what comes after that: Initiating the Vote and Release
emails and doing the discussion. That’s also not too much effort. But to do a
good release a lot of people here should stop their work, download the RC,
build it, test it, try it out in their build setup with their (private)
projects and check if all the files are properly licensed and everything is ok
from a legal point of view. This is a lot of work.
Right now, with the Maven SNAPSHOTs I think we reduced the need to release
often, especially since the ASF Jenkins build is back to blue (the ok state),
but I guess for people using FB and Ant it’s more difficult to keep their
setups up-to-date without re installing the nightly every now and then. But
thinking of it … there is probably no difference for them to install the latest
nightly or the latest release … I have no real opinion on this.
Chris
Am 18.04.17, 09:24 schrieb "OK" <p...@olafkrueger.net>:
>Are you volunteering to be the release manager?
Maybe some day if I understand FlexJS better and know what's necessary to
cut a release...
>Releases have historically been a lot of effort.
It's a bit uncomfortable to speak about effort while contributing nothing by
myself but I also could imagine that more releases are less work at the end.
Is it so much effort cause of so many tasks that has to be done or are there
other reasons?
Maybe there are possibilities to reduce the effort for minor releases?
E.g. IMO there's no need to do all the public relations work for minor
releases which maybe contain just bug fixes.
Thanks,
Olaf
--
View this message in context:
http://apache-flex-development.2333347.n4.nabble.com/FlexJS-Release-cycles-tp61159p61180.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
