Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "WTP/Retention Policy"

< WTP
(Zip Builds for patches or update sites)
(Update sites)
 
(19 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
== Retention Policy for WTP builds ==
 
== Retention Policy for WTP builds ==
  
=== Builds in zip files ===
+
=== Git sources ===
  
Formal releases are kept forever, but only the most recent release is kept on the main download page. Other, older build can be found on the eclipse archive site.  
+
Any code included in a release is left in a git branch forever, but may be deleted from the master branch.  
  
While developing a new releases milestone builds are kept until the release, at which point they are deleted.  
+
Branches are created for convenience and follow one of two conventions: R3.10.x or R3_10_maintenance. Starting with 3.11, maintenance builds are highly unlikely to be done, since minor releases will be released every 13 weeks.
  
Similarly, while developing a milestone, weekly builds are kept until the milestone is available, and then deleted.
+
[https://wiki.eclipse.org/WTP_Gerrit_Access#Clone_a_repository_for_development A list of the current git repos is here].
  
=== Builds on update sites ===  
+
=== Distributions in zip files ===
  
Only the most recent release (and/or patches) are kept on the update site. The goal is to allow users to update to the latest code from what they have installed, but we don't support updating to some previous release. For example, if we come out with a "3.0.3", the "3.0.2" version won't be on the update site any longer. So, someone with "3.0.0" installed could update to "3.0.3", but they could no longer update only to "3.0.2", once 3.0.3 was released.
+
Current releases can be found here: http://download.eclipse.org/webtools/downloads/drops/
  
=== Zip Builds for patches or update sites ===
+
Old releases are archived here: http://archive.eclipse.org/webtools/downloads/drops/
  
These builds are not retained.  
+
While developing a new release, milestone builds are kept until the release, at which point they are deleted.
  
That may seem contradictory, since some of them have been around a long time. But it just means there is no guarantee or predicable time line. The builds are created at the request of committers, usually for some specific adopter problem, and generally not for general use. It's use-at-your-own risk, if someone does want to use it, since hasn't been through the usual review and test cycle.  
+
Similarly, while developing a milestone, weekly integration builds are kept until the milestone is available, and then they are deleted.
  
There are some cases, when updates are created are created in the form of feature patches and put on the public update site. These require PMC review/approval since could effect general users and adopters. These patches on the update site will only be retained until the next release.
+
=== Update sites ===
  
=== Complicating Situations ===
+
The following update sites are composites of the most recent milestones or releases for a given stream. They are guaranteed to work for a couple years.
  
The above rules apply to each sub-project within WTP, so occasionally, a project can have an off cycle release. In this case, "older" releases of a project would be kept on an update site, if needed by other projects within WTP. For example, Dali might come out with a "2.1.1", and the "2.1.0" would be removed, but Dali "2.0.4" would also be kept, since WTP 3.0.4 was depending it.  
+
If they stop working, just [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=WTP%20Releng open a bug].
 +
 +
http://download.eclipse.org/webtools/repository/latest/
  
=== What if these policies don't work for you? ===
+
http://download.eclipse.org/webtools/repository/photon/
 
+
http://download.eclipse.org/webtools/repository/oxygen/
Just ask. Open a bug or post a note to wtp-releng and request what you need left on update site.  
+
http://download.eclipse.org/webtools/repository/neon/
This might happen, for example, if an adopter built a product on, say, "3.0.2" and they are unable to move up or test to the latest "3.0.4" until some future date, so that adopter might need to direct their users to update specifically to "3.0.2".
+
http://download.eclipse.org/webtools/repository/mars/
 
+
Even if a problem is found in retrospect, update sites can usually be restored to some previous state, since we have the basic data duplicated in the archive system and cvs.
+
 
+
In other words, we are glad to be accommodating, but don't want accommodate every hypothetical combination, since it's more work for us and higher disk and transmission load on the Eclipse mirroring system. So, let us know.  
+
  
 +
=== Zip files for patches or update sites ===
  
 +
The [http://download.eclipse.org/webtools/patches/ patch builds] are not guaranteed to be retained, but may survive for some time.
  
 +
Granted, some of them have been around a long time, but there is no guarantee or predicable time line. The builds are created at the request of committers, usually for some specific adopter problem, and generally not for general use. They are use-at-your-own risk, if someone does want to use it, since hasn't been through the usual review and test cycle.
  
 +
There are some cases, when updates are created in the form of feature patches and put on the public update site. These require PMC review/approval since could effect general users and all adopters. These patches on the update site will follow the update site repository policy.
  
 +
After WTP 3.10, patch builds will only be done VERY SPARINGLY for blocker issues, since a new minor release is no more than 13 weeks away, and CI builds are available all the time as commits are pushed to master branch.
  
 +
=== Getting Help, Getting Started, Contributing ===
  
 +
If the above schedule doesn't meet your needs, feel free to contribute to the project! We're always looking for new hands, eyes, and brains.
  
 +
* [https://wiki.eclipse.org/WTP_Gerrit_Access#Clone_a_repository_for_development Clone a repo, and check out the code]
 +
* [https://bugs.eclipse.org/bugs/enter_bug.cgi?classification=WebTools Submit a Bugzilla]
 +
* [https://git.eclipse.org/r/#/dashboard/self Monitor your gerrit submissions]
 +
* [https://wiki.eclipse.org/WTP_Whos_Who Find a committer, project lead, or PMC member]
 +
* [https://wiki.eclipse.org/Category:Eclipse_Web_Tools_Platform_Project All the WTP Wiki pages]
  
 
[[Category:Eclipse Web Tools Platform Project]][[Category:Process and Policies| ]]
 
[[Category:Eclipse Web Tools Platform Project]][[Category:Process and Policies| ]]
 +
[[Category:WTP Releng]]

Latest revision as of 09:49, 4 July 2018

Retention Policy for WTP builds

Git sources

Any code included in a release is left in a git branch forever, but may be deleted from the master branch.

Branches are created for convenience and follow one of two conventions: R3.10.x or R3_10_maintenance. Starting with 3.11, maintenance builds are highly unlikely to be done, since minor releases will be released every 13 weeks.

A list of the current git repos is here.

Distributions in zip files

Current releases can be found here: http://download.eclipse.org/webtools/downloads/drops/

Old releases are archived here: http://archive.eclipse.org/webtools/downloads/drops/

While developing a new release, milestone builds are kept until the release, at which point they are deleted.

Similarly, while developing a milestone, weekly integration builds are kept until the milestone is available, and then they are deleted.

Update sites

The following update sites are composites of the most recent milestones or releases for a given stream. They are guaranteed to work for a couple years.

If they stop working, just open a bug.

http://download.eclipse.org/webtools/repository/latest/
http://download.eclipse.org/webtools/repository/photon/
http://download.eclipse.org/webtools/repository/oxygen/
http://download.eclipse.org/webtools/repository/neon/
http://download.eclipse.org/webtools/repository/mars/

Zip files for patches or update sites

The patch builds are not guaranteed to be retained, but may survive for some time.

Granted, some of them have been around a long time, but there is no guarantee or predicable time line. The builds are created at the request of committers, usually for some specific adopter problem, and generally not for general use. They are use-at-your-own risk, if someone does want to use it, since hasn't been through the usual review and test cycle.

There are some cases, when updates are created in the form of feature patches and put on the public update site. These require PMC review/approval since could effect general users and all adopters. These patches on the update site will follow the update site repository policy.

After WTP 3.10, patch builds will only be done VERY SPARINGLY for blocker issues, since a new minor release is no more than 13 weeks away, and CI builds are available all the time as commits are pushed to master branch.

Getting Help, Getting Started, Contributing

If the above schedule doesn't meet your needs, feel free to contribute to the project! We're always looking for new hands, eyes, and brains.

Back to the top