[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ecf-dev] ECF 3.4 Release...we're a go for Oct 29, 2010
- From: Scott Lewis <slewis@xxxxxxxxxxxxx>
- Date: Mon, 25 Oct 2010 11:12:22 -0700
- Delivered-to: firstname.lastname@example.org
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:184.108.40.206) Gecko/20101013 Lightning/1.0b2 Thunderbird/3.1.5
A couple of more requests:
1) if you write a blog...or want to write a blog...please consider
making some postings about ECF 3.4 (new things, usage experience, etc)
on your blog, in order to help promote ECF, and make people aware of
what a good thing we've got going with remote services (in particular).
Blogging about other things is fine as well. We can use all the
marketing/promotion help we can get from the community.
If you do so, please let me know and I'll add links to the ECF homepage
to the blog entries.
And one final thing...
2) since we've moved to git, there are a number of things that are
broken on the ECF wiki and eclipse.org website content...e.g. links to
project set files are now inappropriate/irrelevant, there is out of date
content describing how to access the ECF source code (e.g. ), and
things like that.
Any help you (the community) can provide in identifying and fixing these
doc problems will be highly appreciated. If you would like to
contribute/fix some of these problems, please
a) open a new bug (with [doc] in subject) describing where/what the
problem is (for example: ).
b) assign the bug to yourself, and indicate that you are working on a fix
c) if in the wiki, you can fix yourself (and then resolve the bug as fixed)
d) if for the website (i.e. at http://www.eclipse.org/ecf), you can
create a patch and attach to the bug you created. Then one of the
committers will apply and resolve the bug.
Thanksinadvance. The move to git will be a great thing for our
community, and so helping us update the ECF docs will be good for everyone.
On 10/25/2010 11:01 AM, Scott Lewis wrote:
An update on the ECF 3.4 release.
Short version: We're a go for ECF 3.4 release on Friday, Oct 29, 2010
(this coming friday).
With lots of releng work from both Markus K (thanks!) and myself,
we're ready to go for this Friday's ECF 3.4 release. Markus has
created a Release_3_4 branch in git , and we now have a build job
 that is building off that branch (and not master).
Requests of committers and contributors:
1) If you have additions and changes intended for *ECF 3.5* but not
ECF 3.4, you may now push those things to master. I would ask that if
you do this, however, that you please take care to try to not break
the build jobs . Actually, the previous sentence applies *all the
time*...please, when you push changes, additions, etc to master, it's
important that you
a) Do not break any build jobs. If build jobs become broken, someone
(perhaps me, perhaps Markus) will come after you electronically pretty
quickly...i.e. to fix whatever it is broke the build job. If things
aren't fixed quickly, we will rollback the committed changes.
b) When/if you push new API or providers to master, at the same time
please try to also add test code (either new test cases or entire new
test plugins) to the appropriate automated tests. For new test
code...please either make sure that the test is passing...or if the
new test code exposes a pre-existing ECF bug, that you open a new bug
describing the exposed problem before adding the test code to the
2) For this week...I would appreciate any help that committers and
contributors can give in doing installation testing before Friday.
What I do for installation testing is this:
a) Using a build from the Release_3_4 job , install the ECF sdk
into Eclipse 3.6.1 (and/or other versions of Eclipse). I usually use
a fresh version of the Eclipse SDK, but that's not necessary. It
should be possible to update existing ECF installations as well.
b) Check the Help->About plugin information...i.e. to make sure the
ECF plugins are correctly installed, and that they contain the correct
c) Run some of the old example apps (e.g. irc client, XMPPS
client...e.g. google talk account, collab client, etc).
d) Sometimes I also import source for the remote services hello
example...i.e. to make sure everything is there to allow people to
view the src, run the example (e.g. the product configuration).
If you do any installation issues and find something wrong that is
severe, please open a bug immediately, and make it major or critical.
Also please set the target milestone to 3.4.0.
This is going to be a very good release for us...coming out just
before ESE (next week), with some very nice new things for
remoteservices, eventadmin, rest API...along with lots of bug fixes
and other contribution...driven by community usage. We're making
I'll make a final 3.4 announcement on this mailing list on Friday 29
(probably in the am pacific time), after the final build has been
completed and promoted to dev.eclipse.org.
Ok...congrats and thanks to all.
ecf-dev mailing list