Hi Emmanuel, Things are definitely moving smoothly; I can say the migration already has been completed and mina.a.o is served from git now.
One thing that may be good to do is add a MOVED_TO_GIT here [1]. MINA has already been disabled from the CMS. Also, the Jenkins job [2] seems to do its job properly [3]. One further improvement to consider may be using docs.mina.a.o as virtual url for static documentation and store all static docs in a single branch (as apposed to the mina-gen-docs and sshd-apidocs branches right now). But IMO that is something to consider in the future when needed. Another thing that needs to be updated is the website publishing workflow [4] which currently still suggests the usage of svn (steps 12 & 14). I can have a look at this as well the next couple of days. Of course if someone beats me to it, no problem at all; in that case feel free to assign me as reviewer ;) [1] https://svn.apache.org/repos/asf/mina/site/trunk/ [2] https://builds.apache.org/job/mina-site/ [3] https://github.com/apache/mina-site/commits/asf-site [4] http://mina.apache.org/mina-project/developer-guide.html On 2020/02/28 09:07:08, Emmanuel Lécharny <[email protected]> wrote: > Hi Roy, > > are things moving smoothly ? When do you think we would be able to done > ? (just wondering, no urgence). > > Thanks a lot ! > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
