Hi Stefan,
Here are some more answers for you:
On 03/02/2013 12:02 PM, Stefan Strobl wrote:
open issues
* currently the release CI build also publishes to
build.eclipse.org/..../babel-tools-nightly -> far from ideal
Using build.eclipse.org for Nightly builds is the best thing to do.
I'm not sure why that is bad?
* we still have to agree on where release artifacts
are published to (download.eclipse.org ?) and if this happens
manually (e.g. build publishes to staging and artifacts are then
copied over directly on the server) or automatically
Released artifacts should go under here:
http://download.eclipse.org/technology/babel/?d
I see we already have a tools-updates-nightly directory. Why don't
we simply create a "tools" directory in which we can divide as such:
download.eclipse.org/technology/babel
`---tools
`----- nightly
`---------- version (0.x.x)
`--- files.zip
`--- updates
`----- release
`---------- version (0.x.x)
`--- files.zip
`--- updates
* how do we announce new releases on the project page?
We need to do a release review. The documentation is exhaustive but
it doesn't take much effort:
http://wiki.eclipse.org/Development_Resources/HOWTO/Release_Reviews
* how do we create release notes, how much support is
there from bugzilla. personally i would really prefer a solution
that just involves listing all bugs with a specific version in
bugzilla (also see my last post to this mailing list)
Eclipse doesn't have a mechanism per se. I will ask on the
cross-project mailing list to see what other projects do.
Denis
that's it for now... looking forward to your feedback!
regards
Stefan
_______________________________________________
babel-dev mailing list
babel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/babel-dev
|