I agree about the documentation. If, indeed, that is the weak point, I will see what I can do to improve it over the coming months. First stop will be to ask folks to indicate what additional doc they would like to see...ah, maybe another wiki page for capturing suggestions.
If 0.98 actually happens in the next couple of months, might we dare to think of 1.0 before the end of the year?? a On Mon, Apr 19, 2021 at 6:36 AM Harbs <harbs.li...@gmail.com> wrote: > I agree with this. > > I personally think that the strongest reason to not call it “1.0” is gaps > in documentation. I wish I was better on that front, and we’d be in big > trouble without Andrew… ;) > > Harbs > > > On Apr 19, 2021, at 11:23 AM, Yishay Weiss <yishayj...@hotmail.com> > wrote: > > > > There are already some Royale apps in production so I think we are ready > for 1.0 in terms of code. Whether to call it 1.0 is probably a marketing > decision at this stage. There will be announcements and (hopefully) > feedback to take care of. > > > > At least that’s how I think of it. > > > > > > > > From: Andrew Wetmore<mailto:cottag...@gmail.com> > > Sent: Sunday, April 18, 2021 3:42 PM > > To: Apache Royale Development<mailto:dev@royale.apache.org> > > Subject: Getting to 1.0 > > > > I know it is not in the nature of Apache projects to have timelines, > since > > each volunteer chooses to work on the task that attracts them. > However...do > > we know what we need to do to get from now (almost 0.9.8) to a 1.0 > release? > > What critical elements are lacking? > > > > For me, there are big gaps in documentation, and I will try to attend to > > some of them. > > > > The release-build process still seems slow and painful, but I don't know > > that that is a blocker to 1.0. > > > > Anything else? > > > > a > > > > -- > > Andrew Wetmore > > > > -- Andrew Wetmore http://cottage14.blogspot.com/
