-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.0.0 Release #1406
Comments
Looks good - want to add fixing the mary-poppins auto-release process. On Sat, May 16, 2015 at 9:26 AM, Friedel Ziegelmayer <
|
@zzo added. Ping me when you have some time I'm happy to help getting this fixed and running (also probably good to have > 1 person being able to check it when there is ab issue) |
@zzo Cleaned up the cruft on canary and remove iojs-1 from travis. Will do the version bump on canary later |
Great what is the process for doing that? thanks On Wed, May 20, 2015 at 9:24 AM, Friedel Ziegelmayer <
|
You need this setup and then run https://github.com/karma-runner/karma-runner.github.com/blob/master/sync-docs.sh which makes a couple of assumptions that you should check before hand (I need to get this documented properly..) On another note I've started with the work for publishing
I feel that this approach would involve a lot less magic and make things easier to understand, to follow (as an outsider) and to maintain (for us). What do you think? |
Most important part, I forgot when to release new "feature" versions: We take a fixed cycle, e.g. every 4 weeks we release a new stable version, bumping version numbers according to semver and the commits. |
@zzo Okay, ignore most of the above, trying to put this into a more understandable and complete form: Suggested release cycle/process: Types of Releases
Release CycleChrome style:
Git Management
Does that make sense to you? What does everyone else think? // cc @karma-runner/contributors |
iojs still not supported |
The master doesn't build with nodejs 2.1.0 because of socket.io. |
@zzo I've given up @karmarunnerbot for now and do the releases manually.. |
What's been happening? Bad npm credentials still? On Fri, May 29, 2015 at 11:12 AM, Friedel Ziegelmayer <
|
No idea :( just not happening anything after it gets send to presubmit, and additionally travis takes > 6h at the moment to process our builds... |
(just merged the stuff that was piling up manually, and will do a release in the next hour or two out of it) |
@zzo going to actually do this :) |
what could go wrong :) what about getting to 1.0 on frameworks & launchers? |
Will bump them one by one over the next weeks as I get to it. |
we can split the list and I can do some as well |
That'd be great, let's get a list in here with checkmarks |
We need to remember to bump the karma dependency to allow for 1.0 when updating them |
sounds good - yep |
Think this is everything - maybe even too much:
|
actually there are other karma repos not owned by karma-runner which will probably need to be updated too - these are just the ones owned by karma-runner |
here is script I want to use to bump version numbers of packages: #!/bin/bash
# Use like: $0 karma-mocha
URL=https://github.com/karma-runner/$1.git
git clone $URL
cd $1
npm install
git remote add upstream $URL
node ../updater.js $1
git commit -a -m 'version bump for 1.0'
git push origin master
grunt release 'updater.js' reads package.json - moves the version number to '1.0.0' and changes all 'dependencies' and 'devDependencies' with the word 'karma' from something like '~0.2.4' to '1.x || ~0.2.4' (ignoring any git url deps like ' "shared-karma-files": "git://github.com/karma-runner/shared-karma-files.git#82ae8d02") What do you think? Here's 'updater.js': var fs = require('fs');
var pjson = JSON.parse(fs.readFileSync('package.json', 'utf8'));
pjson.version = '1.0.0';
pjson = doDeps(pjson, 'dependencies')
pjson = doDeps(pjson, 'devDependencies')
fs.writeFileSync('package.json', JSON.stringify(pjson, null, ' '));
function doDeps(pjson, hashKey) {
if (pjson[hashKey]) {
Object.keys(pjson[hashKey]).forEach(function(key) {
if (key.match(/karma/) && !pjson[hashKey][key].match(/^git/)) {
pjson[hashKey][key] = '1.x || ' + pjson[hashKey][key];
}
});
}
return pjson;
} |
and then once everything is at 1.0 we can go back and remove the '|| ' part |
just ran it on karma-mocha - looks good - will start all the other ones now |
@zzo thanks for getting this started, I didn't have the time for this as I hoped. There is one issue I saw with your releases, that is that you are releasing |
ya that is NOT intended not sure why that is happening - I'll fix before moving on |
ya ok figured it out (but not after accidentally publishing a 2.0 release of karma-junit-reporter which I have fixed :) carrying on... |
ok all of the plugins are updated to 1.0.0 (or 1.0.1 :)) |
It's done :) |
PROFIT! |
do need to mention we can now go back and clean up module deps that have the '1.0 || xxxx' syntax - this can be done as plugins &c actually need to be updated |
There were some notes, and plans about a 1.0 release. I want to use this issue for any discussion and plans around it and start a complete list of tasks to do before we can release.
There is this google doc that was started by @vojtajina and there was #944, which I will close in favor of this issue.
Below is an incomplete list of things that need doing in my opinion.
Organizational
1.0.0
ready state.1.0.0
versions of the frameworks and launchers.0.13.0
with the latest additions.> 1.0
canary
branch and bring it up to date withmaster
iojs-1
from travis (ec4fa02 and d42802a)Improvements
0.10
,0.12
andio.js >= 2.0
Bugs
See the 1.0 Milestone
// cc @zzo @maksimr
Update: I updated the milestone to reflect relevant issues for this.
Update2: Reorganize
The text was updated successfully, but these errors were encountered: