Did a major update for previous versions. It's such a pain if we miss a doc
update for a version X, and we're at version X+2.
At master branch, you update for edge, X+2, X+1 and X folders.
At X+2 branch, you update for edge, X+2, X+1 and X folders.
At X+1 branch, you update for edge, X+1, and X
Are there plans for a *for a saner doc system* ?
--Carlos
On Mon, Jun 24, 2013 at 7:25 PM, Shazron shaz...@gmail.com wrote:
Did a major update for previous versions. It's such a pain if we miss a doc
update for a version X, and we're at version X+2.
At master branch, you update for edge,
Not sure. An idea is one branch per version? So if you work on master, that
is edge. To grab a whole directory of version docs, write a script that
exports the contents of each branch (git-checkout-index) into a folder with
the same branch name (or mapped), then run joDoc (our current tool)
On
Hey guys,
There is no denying that the release branch practice is a little odd for
cordova-docs. This is because the cordova-docs repository versions
everything by directory (a legacy approach that we will someday shift away
from).
I'll hunt down the release wiki article and update it, but here
Makes sense. I'll cherry-pick my changes to the relevant branches.
On Wed, Jun 19, 2013 at 11:45 AM, Michael Brooks
mich...@michaelbrooks.cawrote:
Hey guys,
There is no denying that the release branch practice is a little odd for
cordova-docs. This is because the cordova-docs repository
I noticed in cordova-docs, the 2.8.0 tag was tagged in a commit on master,
but not in the 2.8.x branch. Furthermore, the commit that was tagged is not
even in the 2.8.x branch. Do I fix this?
On Wed, Jun 19, 2013 at 11:51 AM, Shazron shaz...@gmail.com wrote:
Makes sense. I'll cherry-pick my
Rhetorical question of course I am fixing this...
On Wed, Jun 19, 2013 at 1:36 PM, Shazron shaz...@gmail.com wrote:
I noticed in cordova-docs, the 2.8.0 tag was tagged in a commit on master,
but not in the 2.8.x branch. Furthermore, the commit that was tagged is not
even in the 2.8.x branch.
This commit that was tagged 2.8.0:
https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;a=commit;h=1d2fdf5a3344a554136c505b162d1931e878daad
Does not occur in branch 2.8.x:
https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;a=shortlog;h=refs/heads/2.8.x
Nor does the tagged commit
Thanks Shaz!
I was away for JSConf, so another contributor handled the cordova-docs
release for 2.8.0.
Michael
On Wed, Jun 19, 2013 at 1:46 PM, Shazron shaz...@gmail.com wrote:
This commit that was tagged 2.8.0:
On Jun 17, 2013, at 6:21 PM, Shazron shaz...@gmail.com wrote:
Should I bother? I know they will go in edge. There are a couple of issues:
https://issues.apache.org/jira/browse/CB-3753
https://issues.apache.org/jira/browse/CB-3752
Basically it's weird since if I added it to the 2.8.0 folder,
Yeah I'm interested in the flow as well. I think we published everything
again in older releases, not sure if we are still doing that going forward
On Tue, Jun 18, 2013 at 9:30 AM, Marcel Kinard cmarc...@gmail.com wrote:
On Jun 17, 2013, at 6:21 PM, Shazron shaz...@gmail.com wrote:
Should I
Should I bother? I know they will go in edge. There are a couple of issues:
https://issues.apache.org/jira/browse/CB-3753
https://issues.apache.org/jira/browse/CB-3752
Basically it's weird since if I added it to the 2.8.0 folder, it's not in
the 2.8.x branch, but is in master...
So for older
12 matches
Mail list logo
