OK, so do we want: - Always have the release site be the "main" site. - Optionally have a separate SNAPSHOT site.
Do we put this magic in commons-parent? Gary On Sat, Jul 26, 2014 at 7:07 AM, sebb <[email protected]> wrote: > On 25 July 2014 18:03, Stefan Bodewig <[email protected]> wrote: > > On 2014-07-25, Gary Gregory wrote: > > > >> It's that or we agree never to publish a SNAPSHOT site. > > I don't see that as a strict dichotomy. > > > For the record, I do value SNAPSHOT sites so we can also show what we > > are working on. > > That does not necessarily need a whole snapshot site. > A news page would be sufficient in many cases. > > > I'm not convinced we need to enforce the same policy > > for all components. OTOH I don't feel strong enough about it to really > > block a decision that discourages/prohibits SHAPSHOT sites. > > Agreed, so long as the SNAPSHOT site does not replace the site for the > release. > It's vital that users can easily get access to the docs for the > current release(s). > > > Stefan > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- E-Mail: [email protected] | [email protected] Java Persistence with Hibernate, Second Edition <http://www.manning.com/bauer3/> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> Spring Batch in Action <http://www.manning.com/templier/> Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
