On Tue, Apr 29, 2014 at 3:17 PM, Steven Gill <[email protected]> wrote:
> I can take a crack at updating our cadence release process to better > represent dist/. > Awesome! > > I think for the 3.5.0 release, we add package.json files to all platforms > and publish to npm as well as dist. I have created an issue to track this > [1]. This way we can begin work on the CLI post 3.5.0 to use the npm > releases instead of fetching from our git servers. > Good idea. > > I am going to start the release train for 3.5.0 as soon as I add these. > > I say we aim to make 3.5.0 our last cadence release. I'm hoping to switch > to independent platform releases. > > As for docs, I don't think everyone is convinced yet that loosing the > version numbers is the way to go. I say we add version 3.5.0 to docs and > then make the switch to edge for the next cli release. That way it fits > well with this being our last cadence release. > Haven't seen any opposition to this on the list or in your doc. Might as well go to edge now, no? > > We should also take this opportunity to let our community know that 3.5.0 > will be the final cadence release. They should focus on CLI updates from > now on. > No need to announce this until it's ready. Never know what hiccups there might be. > > [1] https://issues.apache.org/jira/browse/CB-6551 > > > On Fri, Apr 25, 2014 at 12:57 PM, Andrew Grieve <[email protected] > >wrote: > > > Would love to get to a platforms-independently-released world, but am > happy > > to do another cadence release. > > > > In terms of getting our act together, we need to update our cadence > release > > process to not have the release to dist/ as an afterthought: > > > > > https://github.com/apache/cordova-coho/blob/master/docs/cadence-release-process.md > > > > Any volunteers for taking a crack at it? Can be edited via pull request > > right on github via clicking the "edit" button: > > > > > https://github.com/apache/cordova-coho/blob/master/docs/cadence-release-process.md > > > > E.g. Need to release to dist/dev *before* npm > > E.g. Don't add -rc1 to versions anymore since those don't create archives > > we can vote on > > E.g. Probably don't need pre-emptive release branches anymore (although I > > think this can be up to each platform to decide on) > > > > > > Another question, can we do this without creating a v3.5.0 of the docs, > as > > in Steve's proposal? > > https://docs > > .google.com/document/d/1qwpypH7sH0wH9Sbesmg8JZow-l8IqdZtF1BtLUZb1As/edit > > > > I think this would be a great time to switch to always edge/. > > > > > > > > > > > > On Fri, Apr 25, 2014 at 3:42 PM, Ian Clelland <[email protected] > > >wrote: > > > > > It's probably time. > > > > > > Joe and I were discussing the possibility of including an (alpha) API > for > > > pluggable webviews in a 3.5.0 release of cordova-android. I'd like to > see > > > that in place, but it would probably not be ready until mid-next-week > at > > > the earliest. > > > > > > iOS has had only a couple of commits since 3.4.1, so there's no rush > > there. > > > I have no doubt that the other platforms are overdue for a release, > > though. > > > > > > > > > On Fri, Apr 25, 2014 at 3:34 PM, Jesse <[email protected]> > wrote: > > > > > > > There are numerous changes I would like to see pushed out. Can we > start > > > > talking about a 3.5.0 platform release? > > > > > > > > > > > > @purplecabbage > > > > risingj.com > > > > > > > > > >
