uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marshall Schor (JIRA)" <...@uima.apache.org>
Subject [jira] [Updated] (UIMA-3248) building Eclipse Update SItes - use better method for release
Date Thu, 05 Sep 2013 14:00:53 GMT

     [ https://issues.apache.org/jira/browse/UIMA-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Marshall Schor updated UIMA-3248:
---------------------------------

    Description: 
The current build for an Eclipse release achieves "safety" (from accidentally promoting a
release before it's ready) by doing 2 distr.apache.org..../dev/ commits:  one to delete the
current copy of the update-site, the other to "copy" the current update site to the /dev/
spot.

I tried an improved method having 0 commits, which uses "switch" - checkout from ...release
and then a local switch to ...dev.  However that didn't work, see the question and response
here: http://markmail.org/thread/xcpyyezj6ourgbez#query:+page:1+mid:2eqyo3xmxldy2uoi+state:results

So I'm changing this to remove the "safety".  This means the update site build, when done
with -Papache-release (which is applied either by the mvn user or by the mvn release:... plugin),
will svn checkout into the target spot for the eclipse update subsite, the existing update
subsite, from ...Release.

Which means, that after the new site has been built, and the release vote has passed, you
can commit the changes right back to the ...release spot.

If by accident you commit before you want to, you can always manually fix this by reverting
that commit.  So it doesn't have too much downside - the real downside is that SVN hook on
commits which launching "mirroring" of the changes the 100's of sites mirroring the Apache
distribution.

The update site, when done without -Papache-release, does no svn checkout from the .../release
update site.   Your "test" update site will be OK, but will be missing previous releases.
 If you need the previous releases, run with the -Papache-release.

  was:
The current build for an Eclipse release achieves "safety" (from accidentally promoting a
release before it's ready) by doing 2 distr.apache.org..../dev/ commits:  one to delete the
current copy of the update-site, the other to "copy" the current update site to the /dev/
spot.

The improved method: (0 commits): 

1) checkout from release -> target/eclipse-update-site/[subsite]
2) svn switch that checkout spot to /dev/

I tried this, and it fails to do the "right" thing; if it finds a working copy file is not
in the switched-to directory, it deletes it in the working copy. This is a problem...

...
do builds / votes / etc.  When done, 
3) svn switch that checkout spot back to /release/
4) commit (and therefore publish to the mirrors) the change.

    
> building Eclipse Update SItes - use better method for release
> -------------------------------------------------------------
>
>                 Key: UIMA-3248
>                 URL: https://issues.apache.org/jira/browse/UIMA-3248
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Build, Packaging and Test
>    Affects Versions: parent-pom-6
>            Reporter: Marshall Schor
>            Priority: Minor
>             Fix For: parent-pom-7
>
>
> The current build for an Eclipse release achieves "safety" (from accidentally promoting
a release before it's ready) by doing 2 distr.apache.org..../dev/ commits:  one to delete
the current copy of the update-site, the other to "copy" the current update site to the /dev/
spot.
> I tried an improved method having 0 commits, which uses "switch" - checkout from ...release
and then a local switch to ...dev.  However that didn't work, see the question and response
> here: http://markmail.org/thread/xcpyyezj6ourgbez#query:+page:1+mid:2eqyo3xmxldy2uoi+state:results
> So I'm changing this to remove the "safety".  This means the update site build, when
done with -Papache-release (which is applied either by the mvn user or by the mvn release:...
plugin), will svn checkout into the target spot for the eclipse update subsite, the existing
update subsite, from ...Release.
> Which means, that after the new site has been built, and the release vote has passed,
you can commit the changes right back to the ...release spot.
> If by accident you commit before you want to, you can always manually fix this by reverting
that commit.  So it doesn't have too much downside - the real downside is that SVN hook on
commits which launching "mirroring" of the changes the 100's of sites mirroring the Apache
distribution.
> The update site, when done without -Papache-release, does no svn checkout from the .../release
update site.   Your "test" update site will be OK, but will be missing previous releases.
 If you need the previous releases, run with the -Papache-release.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message