I don't have a strong opinion but I'm not sure we even need releases for the content. Various websites are also just updated without a release process - including apache.org itself.
I'm not a big fan on voting for releases every time we fix a typo but I'm not sure if the other extreme - no releases - is any better... On Fri, Jan 10, 2020 at 10:30 AM Ryan Skraba <[email protected]> wrote: > Hello! > > Is there some documentation or discussion about how > presentations/resources/the project is released? From some previous > messages, it seems like we plan on releasing training resources > individually (such as ApacheWay Training 1.0, Ignite Training 1.1). > > I imagine that incubation is the right time and place to work out > details of the process (voting per presentation release, tags, > publishing artifacts, where to announce/list published content > releases, etc). > > A snapshot version of a presentation in /content can depend on the > snapshot version of resources and parent right? I'd love to see one > of the existing presentations redone on top of the archetype to prove > and test it. I can give it a try on the /content/spark/1-basics > presentation at https://github.com/apache/incubator-training/pull/59 > if you'd like, but I'm just plodding away on that content when I have > some spare time. > > Or do you think it would be best to just do a release of these > artifacts and work out the kinks based on that experience? > > Best regards, Ryan > > > > > On Tue, Jan 7, 2020 at 11:41 AM Christofer Dutz > <[email protected]> wrote: > > > > Hi all, > > > > in order to really use the changes I just pushed, we should probably > fine tune them (especially the CSS and static resources) and do a first > release soon. > > Otherwise other presentations can’t be released based on them. > > > > Chris >
