Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 365414

Summary: Strategy for releasing doc.isv plug-ins
Product: [Eclipse Project] Platform Reporter: Markus Keller <markus.kell.r>
Component: RelengAssignee: Platform-Releng-Inbox <platform-releng-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: daniel_megert, deepakazad, john.arthorne, kim.moir, pwebster
Version: 3.8   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Markus Keller CLA 2011-12-02 07:26:47 EST 
With the automatic tagging and releasing from bug 363215, we also need to decide on a strategy on how to tag the ISV doc plug-ins:

org.eclipse.platform.doc.isv
org.eclipse.jdt.doc.isv
org.eclipse.pde.doc.user

These plug-ins contain generated API descriptions from Javadoc and extension points, so they should be released for every build in which any API has changed. Up to now, we just occasionally released these plug-ins, even if nothing changed in the plug-ins.

The optimal strategy is too hard to implement (would have to follow all dependencies and check if any API changed).

The simplest strategy is just to tag these plug-ins with every build. I think we should go for this one.
Comment 1 Kim Moir CLA 2011-12-02 07:49:20 EST 
The issue with tagging the bundles for every build is one of these bundles is quite large.

-bash-3.00$ du -sh *doc.*.pack.gz
3.4M    org.eclipse.jdt.doc.isv_3.8.0.N20111201-2000.jar.pack.gz
19M     org.eclipse.platform.doc.isv_3.8.0.N20111201-2000.jar.pack.gz
6.3M    org.eclipse.platform.doc.user_3.8.0.N20111201-2000.jar.pack.gz

If we tagged the platform.doc.isv every build people would be gratuitously downloading the doc bundle each build.  Has this lack of tagging automatically caused a problem before?
Comment 2 Paul Webster CLA 2011-12-02 07:56:06 EST 
(In reply to comment #1)
> 
> If we tagged the platform.doc.isv every build people would be gratuitously
> downloading the doc bundle each build.  Has this lack of tagging automatically
> caused a problem before?

It means those plugins don't reflect the accurate javadoc, since we'd keep throwing them away until the next tag change.

But I'm not keen on tagging them every time either, org.eclipse.platform.doc.isv_3.8.0.v20111025-1300.jar is 35M unpacked.

PW
Comment 3 Markus Keller CLA 2011-12-02 09:08:47 EST 
> Has this lack of tagging automatically caused a problem before?

Probably not, since the JDT UI team usually tagged them shortly before a milestone. This was just a few clicks with the CVS releng tools, but it's more work with Git (tag, push the tag, update map file, commit, push).

Maybe we could have a simple tag-now.sh in these plug-ins which performs all the steps? Then we could keep the occasional manual releases.
Comment 4 John Arthorne CLA 2011-12-02 09:23:54 EST 

*** This bug has been marked as a duplicate of bug 364980 ***