trafodion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hans Zeller <hans.zel...@esgyn.com>
Subject RE: Website updates /documentation changes for Trafodion 2.1 and 2.2
Date Tue, 28 Mar 2017 00:38:46 GMT
Hi Dave, it may be best to wait with this fork until 2.1 has released. That would mean that
for now our website does not show R2.2 manuals, it only shows the R2.1 manuals as "in development".

If people believe that we need to have the 2.2 manuals on-line right now we should discuss
that here.

Thanks,

Hans

-----Original Message-----
From: Dave Birdsall [mailto:dave.birdsall@esgyn.com] 
Sent: Monday, March 27, 2017 5:28 PM
To: dev@trafodion.incubator.apache.org
Subject: RE: Website updates /documentation changes for Trafodion 2.1 and 2.2

That was probably my fault... I take it we don't fork off the documentation directories into
the release2.1 branch?

-----Original Message-----
From: Sandhya Sundaresan [mailto:sandhya.sundaresan@esgyn.com] 
Sent: Monday, March 27, 2017 5:03 PM
To: dev@trafodion.incubator.apache.org
Subject: RE: Website updates /documentation changes for Trafodion 2.1 and 2.2

Hi everyone,

This is targeted towards Trafodion Committers who are making Website updates. 
   Since we have doc  content  in the Trafodion 2.1 branch (release2.1) that hasn't yet been
merged to Master Trafodion branch , it is important that the Website updates to the Trafodion
documentation website be made only from 2.1 branch for now until the release is officially
done.   A few days ago, all the 2.1 documentation updates we did got overwritten  by a commit/publish
that was done from the Trafodion Master branch.  It got restored today as soon as we noticed
it. 

Thank you
Sandhya

-----Original Message-----
From: Hans Zeller [mailto:hans.zeller@esgyn.com] 
Sent: Tuesday, March 7, 2017 6:04 PM
To: dev@trafodion.incubator.apache.org
Subject: Documentation changes for Trafodion 2.1 and 2.2

Hi,

Since Sandhya has split off the release branch for Trafodion 2.1, documentation changes that
are meant for 2.1 should be checked into that release. You can add documentation for 2.2 features
to the main branch.

As far as I remember, this is the simple approach agreed to by Steve and Gunnar for the 2.0.x
releases. The only caveat is that we can't easily make documentation updates after a release
has shipped. So, make your changes now while it's easy - but talk to Sandhya first, as we
are in the final stretch of 2.1.

Thanks,

Hans

Mime
View raw message