Sounds good to me. For release what do we need to do to the current doc site? Some things I thought of: 1) We should probably try to fix things in the docs like `pio template get` or the link to the old gallery site. 2) Are there any other subdomains that are required to make things work or that are referenced in the docs? 3) Install.sh can be moved to the site to remove the reference to an un-released release. 4) would be nice to get the new gallery page in but I guess the site doesn’t have to sync schedule with code except for version number references. @Marcin, you up for integrating your gallery page with the site?
Interesting to note that only the example templates are in the donation so docs reference non-apache code in many places. On Jul 25, 2016, at 1:01 PM, Donald Szeto <don...@apache.org> wrote: For 4, I have been manually pushing the livedoc site for the first few changes. Hoping to get Jenkins running soon. How about Aug 8 as our first release? Due to all these package name changes, I'd also like to suggest to start a new minor version. How about 0.10.0? Regards, Donald On Sat, Jul 23, 2016 at 7:45 AM, Pat Ferrel <p...@occamsmachete.com> wrote: > I’d like to propose a first minimum release from Apache to include: > > 1) SSL optional (I think @alex has already merged this PR) > 2) Heal ActionML fork > 3) change to Apache class naming and include Apache license notices in all > code > 4) live doc site > 5) Apache classes published to the maven/sbt universe. > > I’ve talked to Alex separately and we are up for doing 1 and 2, and I > think 3 is already a PR. I’ll help with 4 but it sounds like Donald is on > that. If this sounds good can someone propose a date? I can do 2 and other > things on my plate by first week of Aug. > > >
