package-drone-0.11.6

This is a bugfix release for 0.11.x.

The following issue got fixed:

• #142: Failed to create category (XML) generator artifacts

Thanks to @SvenEwald for reporting this issue.

package-drone-0.11.5

This is a bugfix release for 0.11.x.

The following issues got fixed:

• #140: The Bundle-Localization default value was ignored which resulted in missing replacements
• #141: When an exception was thrown inside a channel operation the rollback was not triggered
• Hide drop upload button when user is not manager
• Fix and backport the v2 upload API from eclipse/packagedrone
• Fix a formatting issue in the WWW-Authentication response

Thanks to @SvenEwald and @afischer211 for reporting the issues.

package-drone-0.11.4

This is a bugfix release for 0.11.x.

The following issues got fixed:

• #137: warning messages in mvn deploy when tycho cleaner aspect was present
• Fix downloading issue in YUM adapter

Thanks to @afischer211 for reporting the warning message regression.

package-drone-0.11.3

This is a bugfix release for 0.11.x.

The following issue got fixed:

• Fix P2 generation issue with "null" touchpoint

package-drone-0.11.2

This is a bugfix release for 0.11.x.

The following issue got fixed:

• The channel cache directory did not get cleaned up

package-drone-0.11.1

This is a bugfix release for 0.11.x.

The following issues where fixed:

• Downloading artifacts from an APT repository caused a 404 error
• The package drone user directory was incorrect for RPM installations

package-drone-0.11.0

This is the final release of the 0.11.0 release cycle.

Note: This release of Package Drone does have a different storage mechanism. Therefore is it not possible to simply update the package drone installation. It is necessary to export all channels from the old installation and import them back into the new installation.

Note: This release has different package names (org.eclipse.packagedrone.server) for the RPM and DEB packages, and does declare a conflict on the old package. This is to ensure that when the final release comes there has to be manual intervention, instead of just upgrading the package from the repository, finding out that the store model has changed.

New and noteworthy

The main theme on this release is the new storage backend. This may be considered a new feature and a changed behavior. But in any case it is noteworthy 😉 Read more on this at http://packagedrone.org/2015/10/23/the-upcoming-0-11-0-release/

Changed storage model

The backend storage model, which was JDBC based and did span over several groups of entities was removed and replaced with a backend which considers entities groups (like authentication, configuration and channels) separately. Also has the JDBC storage been completely removed (for now) and was replaced by a simple file based approach. For more information see above.

OBR repository index

Starting with this release Package Drone does support OBR repositories now.

Support for OpenSUSE 13.2

There is an RPM for OpenSUSE 13.2 (dist marker os13) now. It does support systemd and SUSE's firewall mechanism. However OpenSUSE is not that much tested as other distributions. That is why there is no RPM repository for the moment. The RPM files have to be downloaded and installed manually (e.g. using zypper install org.eclipse.packagedrone*.rpm).

Move to Eclipse Foundation

All preparations have been made to submit the source code as "initial contribution" to the Eclipse Foundation for the Eclipse Package Drone project. This includes renaming all package names to org.eclipse.packagedrone and a general restructuring to let the repository structure be more like other Eclipse projects.

Note: Although this release does have package names like org.eclipse.packagedrone this is still not an official Eclipse release!

In the same step the RPM and DEB packages were also renamed. See above.

Performance improvements

Again performance improvements have been made. Especially when aggregating P2 repositories in the end of a channel operation.

GoogleBot

GoogleBot requests are now intercepted and the generation of "jsessionid" is disabled.

Changed behavior

• Channels IDs are prefixed with apm_ now
• This release does not longer store content in Postgres, MySQL or any other JDBC database. It is also incapable of reading any stored information prior to the 0.11.0 release.
• The RPM and DEB package names have been changed

Note: Again, this version does have different RPM/DEB package names, which conflict with the old package names. And the content of the old (before 0.11.0) Package Drone instance has to be exported and re-imported in the new (0.11.0) instance.

Improvements and bug fixes

Of course a few bugs got fixed as well 😉

package-drone-0.11.0-rc1

This is a release release for the upcoming release 0.11.0.

Warning: This release of Package Drone does have a different storage mechanism. Therefore is it not possible to simply update the package drone installation. It is necessary to export all channels from the old installation and import them back into the new installation.

Warning: This release has different package names (org.eclipse.packagedrone.server) for the RPM and DEB packages, and does declare a conflict on the old package. This is to ensure that when the final release comes there has to be manual intervention, instead of just upgrading the package from the repository, finding out that the store model has changed.

See also: https://github.com/ctron/package-drone/releases/tag/v0.11.0-m1

This version is a stable release candidate which passed all unit, integration and stress/performance tests. There are no breaking changes planned for the final release.

package-drone-0.11.0-m5

This is a milestone release towards the upcoming release 0.11.0.

Warning: This release of Package Drone does have a different storage mechanism. Therefore is it not possible to simply update the package drone installation. It is necessary to export all channels from the old installation and import them back into the new installation.

See also: https://github.com/ctron/package-drone/releases/tag/v0.11.0-m1

This version is a stable milestone version, which passed all unit, integration and stress/performance tests. However there may be breaking changes up to the final 0.11.0 release.

Changes in this release

• performance improvements and cleanups for the channel storage model
• fix the Oomph setup
• #132: add a workaround to show channels which are currently to big for the browser to render

package-drone-0.11.0-m4

This is a milestone release towards the upcoming release 0.11.0.

Warning: This release of Package Drone does have a different storage mechanism. Therefore is it not possible to simply update the package drone installation. It is necessary to export all channels from the old installation and import them back into the new installation.

See also: https://github.com/ctron/package-drone/releases/tag/v0.11.0-m1

This version is a stable milestone version, which passed all unit, integration and stress/performance tests. However there may be breaking changes up to the final 0.11.0 release.

Changes in this release

The most notable change is the re-structured P2 repository generation process. Instead of parsing each XML fragment during the channel aggregation phase, this is done now during the metadata extraction phase. In the final aggregation phase only string snippets are concatenated, which results in a far better performance when adding artifacts later on.

The (hopefully for now) most un-noted change is the change to org.eclipse.packagedrone for the namespace. This allowed us to finally submit our initial contribution.

Beside that a few bugs got fixed as well 😉