Discussion:
[VOTE] Release Apache Sling IDE Tooling 1.0.0
(too old to reply)
Robert Munteanu
2014-06-23 11:58:12 UTC
Permalink
Hi,

We solved 140 issues in this release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12324873

There are still some outstanding issues:
https://issues.apache.org/jira/browse/SLING/component/12320908

The release candidate has been uploaded at
https://dist.apache.org/repos/dist/dev/sling,
and can be built using

mvn clean package

The resulting binaries can be installed into an Eclipse instance by
installing from the update site which is found at
p2update/target/repository after building the project.

Please vote to approve this release:

[ ] +1 Approve the release
[ ] 0 Don't care
[ ] -1 Don't release, because ...

This majority vote is open for at least 72 hours

Thanks,

Robert
Robert Munteanu
2014-06-23 11:58:42 UTC
Permalink
+1

Robert
Post by Robert Munteanu
Hi,
https://issues.apache.org/jira/browse/SLING/fixforversion/12324873
https://issues.apache.org/jira/browse/SLING/component/12320908
The release candidate has been uploaded at
https://dist.apache.org/repos/dist/dev/sling,
and can be built using
mvn clean package
The resulting binaries can be installed into an Eclipse instance by
installing from the update site which is found at
p2update/target/repository after building the project.
[ ] +1 Approve the release
[ ] 0 Don't care
[ ] -1 Don't release, because ...
This majority vote is open for at least 72 hours
Thanks,
Robert
Konrad Windszus
2014-06-23 12:19:56 UTC
Permalink
I just tested it and get the following exception when trying to export or import content via Right click “Sling -> Export Content” on a content project which was already added as a module to the Sling Server:

The selected project is not configured with/added to any Sling server.

Do you want me to open a bug about that?

Thanks,
Konrad
Post by Robert Munteanu
Hi,
https://issues.apache.org/jira/browse/SLING/fixforversion/12324873
https://issues.apache.org/jira/browse/SLING/component/12320908
The release candidate has been uploaded at
https://dist.apache.org/repos/dist/dev/sling,
and can be built using
mvn clean package
The resulting binaries can be installed into an Eclipse instance by
installing from the update site which is found at
p2update/target/repository after building the project.
[ ] +1 Approve the release
[ ] 0 Don't care
[ ] -1 Don't release, because ...
This majority vote is open for at least 72 hours
Thanks,
Robert
Robert Munteanu
2014-06-23 12:25:25 UTC
Permalink
Post by Konrad Windszus
The selected project is not configured with/added to any Sling server.
Do you want me to open a bug about that?
Please do, since I can't reproduce it locally.

Thanks,

Robert
Post by Konrad Windszus
Thanks,
Konrad
Post by Robert Munteanu
Hi,
https://issues.apache.org/jira/browse/SLING/fixforversion/12324873
https://issues.apache.org/jira/browse/SLING/component/12320908
The release candidate has been uploaded at
https://dist.apache.org/repos/dist/dev/sling,
and can be built using
mvn clean package
The resulting binaries can be installed into an Eclipse instance by
installing from the update site which is found at
p2update/target/repository after building the project.
[ ] +1 Approve the release
[ ] 0 Don't care
[ ] -1 Don't release, because ...
This majority vote is open for at least 72 hours
Thanks,
Robert
Konrad Windszus
2014-06-23 13:16:42 UTC
Permalink
Post by Robert Munteanu
Post by Konrad Windszus
The selected project is not configured with/added to any Sling server.
Do you want me to open a bug about that?
Please do, since I can't reproduce it locally.
Done with https://issues.apache.org/jira/browse/SLING-3687
Post by Robert Munteanu
Thanks,
Robert
Post by Konrad Windszus
Thanks,
Konrad
Post by Robert Munteanu
Hi,
https://issues.apache.org/jira/browse/SLING/fixforversion/12324873
https://issues.apache.org/jira/browse/SLING/component/12320908
The release candidate has been uploaded at
https://dist.apache.org/repos/dist/dev/sling,
and can be built using
mvn clean package
The resulting binaries can be installed into an Eclipse instance by
installing from the update site which is found at
p2update/target/repository after building the project.
[ ] +1 Approve the release
[ ] 0 Don't care
[ ] -1 Don't release, because ...
This majority vote is open for at least 72 hours
Thanks,
Robert
Robert Munteanu
2014-06-23 14:35:47 UTC
Permalink
Post by Konrad Windszus
Post by Robert Munteanu
Post by Konrad Windszus
The selected project is not configured with/added to any Sling server.
Do you want me to open a bug about that?
Please do, since I can't reproduce it locally.
Done with https://issues.apache.org/jira/browse/SLING-3687
Konrad has provided a fix for this issue and I've applied it for version 1.0.2 .

Given that the reported problem occurs only non-standard scenarios,
I'm going to continue the release vote and incorporate the fix only
for the next version.

Robert
Post by Konrad Windszus
Post by Robert Munteanu
Thanks,
Robert
Post by Konrad Windszus
Thanks,
Konrad
Post by Robert Munteanu
Hi,
https://issues.apache.org/jira/browse/SLING/fixforversion/12324873
https://issues.apache.org/jira/browse/SLING/component/12320908
The release candidate has been uploaded at
https://dist.apache.org/repos/dist/dev/sling,
and can be built using
mvn clean package
The resulting binaries can be installed into an Eclipse instance by
installing from the update site which is found at
p2update/target/repository after building the project.
[ ] +1 Approve the release
[ ] 0 Don't care
[ ] -1 Don't release, because ...
This majority vote is open for at least 72 hours
Thanks,
Robert
--
Sent from my (old) computer
Robert Munteanu
2014-06-25 07:45:23 UTC
Permalink
I realized that a file has been checked in with an incorrect copyright header

https://svn.apache.org/repos/asf/sling/tags/sling-ide-tooling-1.0.0/eclipse-ui/src/org/apache/sling/ide/eclipse/ui/wizards/AbstractNewSlingApplicationWizard.java

This vote is therefore cancelled and will be restarted after a fix has
been applied.

Robert
Post by Robert Munteanu
Post by Konrad Windszus
Post by Robert Munteanu
Post by Konrad Windszus
The selected project is not configured with/added to any Sling server.
Do you want me to open a bug about that?
Please do, since I can't reproduce it locally.
Done with https://issues.apache.org/jira/browse/SLING-3687
Konrad has provided a fix for this issue and I've applied it for version 1.0.2 .
Given that the reported problem occurs only non-standard scenarios,
I'm going to continue the release vote and incorporate the fix only
for the next version.
Robert
Post by Konrad Windszus
Post by Robert Munteanu
Thanks,
Robert
Post by Konrad Windszus
Thanks,
Konrad
Post by Robert Munteanu
Hi,
https://issues.apache.org/jira/browse/SLING/fixforversion/12324873
https://issues.apache.org/jira/browse/SLING/component/12320908
The release candidate has been uploaded at
https://dist.apache.org/repos/dist/dev/sling,
and can be built using
mvn clean package
The resulting binaries can be installed into an Eclipse instance by
installing from the update site which is found at
p2update/target/repository after building the project.
[ ] +1 Approve the release
[ ] 0 Don't care
[ ] -1 Don't release, because ...
This majority vote is open for at least 72 hours
Thanks,
Robert
--
Sent from my (old) computer
--
Sent from my (old) computer
Robert Munteanu
2014-06-26 08:32:26 UTC
Permalink
Hi,

We solved 144 issues in this release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12324873

There are still some outstanding issues:
https://issues.apache.org/jira/browse/SLING/component/12320908

The release candidate has been uploaded at
https://dist.apache.org/repos/dist/dev/sling,
and can be built using

mvn clean package

The resulting binaries can be installed into an Eclipse instance by
installing from the update site which is found at
p2update/target/repository after building the project.

Please vote to approve this release:

[ ] +1 Approve the release
[ ] 0 Don't care
[ ] -1 Don't release, because ...

This majority vote is open for at least 72 hours.
Robert Munteanu
2014-06-29 19:32:55 UTC
Permalink
Anyone?

Robert
Post by Robert Munteanu
Hi,
https://issues.apache.org/jira/browse/SLING/fixforversion/12324873
https://issues.apache.org/jira/browse/SLING/component/12320908
The release candidate has been uploaded at
https://dist.apache.org/repos/dist/dev/sling,
and can be built using
mvn clean package
The resulting binaries can be installed into an Eclipse instance by
installing from the update site which is found at
p2update/target/repository after building the project.
[ ] +1 Approve the release
[ ] 0 Don't care
[ ] -1 Don't release, because ...
This majority vote is open for at least 72 hours.
Carsten Ziegeler
2014-06-30 05:57:12 UTC
Permalink
Why is this release not following the normal release procedure and
available via the staging maven repo?

Carsten
Post by Robert Munteanu
Anyone?
Robert
Post by Robert Munteanu
Hi,
https://issues.apache.org/jira/browse/SLING/fixforversion/12324873
https://issues.apache.org/jira/browse/SLING/component/12320908
The release candidate has been uploaded at
https://dist.apache.org/repos/dist/dev/sling,
and can be built using
mvn clean package
The resulting binaries can be installed into an Eclipse instance by
installing from the update site which is found at
p2update/target/repository after building the project.
[ ] +1 Approve the release
[ ] 0 Don't care
[ ] -1 Don't release, because ...
This majority vote is open for at least 72 hours.
--
Carsten Ziegeler
Adobe Research Switzerland
cziegeler-1oDqGaOF3Lkdnm+***@public.gmane.org
Robert Munteanu
2014-06-30 08:06:36 UTC
Permalink
Hi Carsten,
Post by Carsten Ziegeler
Why is this release not following the normal release procedure and
available via the staging maven repo?
There are two main reasons.

1. While the build is driven by Maven, building Eclipse plug-ins with
Tycho means that some of the regular Maven plugins don't work. For
instance, the source and javadoc plugin, see [1],[2] . Since IIUC the
release is based on the source code, and the binaries are just for
convenience, I opted not to make the release run on the output of
individual projects, but on the whole source zip.

2. If I were to deploy the plug-ins by themselves to the repo, it
would not be trivial to assemble back an p2/Eclipse update which can
be used to test the functionality of the release.

That being said, I'd be more than happy to refine this process, so
suggestions on how to do that are welcome :-)

Thanks,

Robert


[1]: https://dev.eclipse.org/mhonarc/lists/tycho-user/msg05730.html
[2]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=398061
Post by Carsten Ziegeler
Carsten
Post by Robert Munteanu
Anyone?
Robert
Post by Robert Munteanu
Hi,
https://issues.apache.org/jira/browse/SLING/fixforversion/12324873
https://issues.apache.org/jira/browse/SLING/component/12320908
The release candidate has been uploaded at
https://dist.apache.org/repos/dist/dev/sling,
and can be built using
mvn clean package
The resulting binaries can be installed into an Eclipse instance by
installing from the update site which is found at
p2update/target/repository after building the project.
[ ] +1 Approve the release
[ ] 0 Don't care
[ ] -1 Don't release, because ...
This majority vote is open for at least 72 hours.
--
Carsten Ziegeler
Adobe Research Switzerland
Carsten Ziegeler
2014-06-30 10:53:09 UTC
Permalink
Thanks for the info, Robert - I'm not sure what the best approach is,
however the zip now contains 1.0.0-SNAPSHOT as versions but I guess the
final release should be 1.0.0. This would mean we're voting on something
which is then not released. On the other hand, if we put up 1.0.0 in a
globally available space everyone can simply download it from there and
voting, especially withdrawing the release is way harder.

Carsten
Post by Robert Munteanu
Hi Carsten,
Post by Carsten Ziegeler
Why is this release not following the normal release procedure and
available via the staging maven repo?
There are two main reasons.
1. While the build is driven by Maven, building Eclipse plug-ins with
Tycho means that some of the regular Maven plugins don't work. For
instance, the source and javadoc plugin, see [1],[2] . Since IIUC the
release is based on the source code, and the binaries are just for
convenience, I opted not to make the release run on the output of
individual projects, but on the whole source zip.
2. If I were to deploy the plug-ins by themselves to the repo, it
would not be trivial to assemble back an p2/Eclipse update which can
be used to test the functionality of the release.
That being said, I'd be more than happy to refine this process, so
suggestions on how to do that are welcome :-)
Thanks,
Robert
[1]: https://dev.eclipse.org/mhonarc/lists/tycho-user/msg05730.html
[2]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=398061
Post by Carsten Ziegeler
Carsten
Post by Robert Munteanu
Anyone?
Robert
Post by Robert Munteanu
Hi,
https://issues.apache.org/jira/browse/SLING/fixforversion/12324873
https://issues.apache.org/jira/browse/SLING/component/12320908
The release candidate has been uploaded at
https://dist.apache.org/repos/dist/dev/sling,
and can be built using
mvn clean package
The resulting binaries can be installed into an Eclipse instance by
installing from the update site which is found at
p2update/target/repository after building the project.
[ ] +1 Approve the release
[ ] 0 Don't care
[ ] -1 Don't release, because ...
This majority vote is open for at least 72 hours.
--
Carsten Ziegeler
Adobe Research Switzerland
--
Carsten Ziegeler
Adobe Research Switzerland
cziegeler-1oDqGaOF3Lkdnm+***@public.gmane.org
Justin Edelson
2014-06-30 15:56:38 UTC
Permalink
Robert-
Are you going to re-call the vote? I see some activity from you which
makes it look like you are.

Regards,
Justin
Post by Carsten Ziegeler
Thanks for the info, Robert - I'm not sure what the best approach is,
however the zip now contains 1.0.0-SNAPSHOT as versions but I guess the
final release should be 1.0.0. This would mean we're voting on something
which is then not released. On the other hand, if we put up 1.0.0 in a
globally available space everyone can simply download it from there and
voting, especially withdrawing the release is way harder.
Carsten
Post by Robert Munteanu
Hi Carsten,
Post by Carsten Ziegeler
Why is this release not following the normal release procedure and
available via the staging maven repo?
There are two main reasons.
1. While the build is driven by Maven, building Eclipse plug-ins with
Tycho means that some of the regular Maven plugins don't work. For
instance, the source and javadoc plugin, see [1],[2] . Since IIUC the
release is based on the source code, and the binaries are just for
convenience, I opted not to make the release run on the output of
individual projects, but on the whole source zip.
2. If I were to deploy the plug-ins by themselves to the repo, it
would not be trivial to assemble back an p2/Eclipse update which can
be used to test the functionality of the release.
That being said, I'd be more than happy to refine this process, so
suggestions on how to do that are welcome :-)
Thanks,
Robert
[1]: https://dev.eclipse.org/mhonarc/lists/tycho-user/msg05730.html
[2]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=398061
Post by Carsten Ziegeler
Carsten
Post by Robert Munteanu
Anyone?
Robert
Post by Robert Munteanu
Hi,
https://issues.apache.org/jira/browse/SLING/fixforversion/12324873
https://issues.apache.org/jira/browse/SLING/component/12320908
The release candidate has been uploaded at
https://dist.apache.org/repos/dist/dev/sling,
and can be built using
mvn clean package
The resulting binaries can be installed into an Eclipse instance by
installing from the update site which is found at
p2update/target/repository after building the project.
[ ] +1 Approve the release
[ ] 0 Don't care
[ ] -1 Don't release, because ...
This majority vote is open for at least 72 hours.
--
Carsten Ziegeler
Adobe Research Switzerland
--
Carsten Ziegeler
Adobe Research Switzerland
Robert Munteanu
2014-06-30 16:04:31 UTC
Permalink
I'm in the process of re-staging the release on repository.apache.org.
I'll send more details once I've validated the repo using
check_staged_release.sh .

Unfortunately this seems to take a lot of time due to the number of
released artifacts - 25 minutes and counting.

On Mon, Jun 30, 2014 at 6:56 PM, Justin Edelson
Post by Justin Edelson
Robert-
Are you going to re-call the vote? I see some activity from you which
makes it look like you are.
Regards,
Justin
Post by Carsten Ziegeler
Thanks for the info, Robert - I'm not sure what the best approach is,
however the zip now contains 1.0.0-SNAPSHOT as versions but I guess the
final release should be 1.0.0. This would mean we're voting on something
which is then not released. On the other hand, if we put up 1.0.0 in a
globally available space everyone can simply download it from there and
voting, especially withdrawing the release is way harder.
Carsten
Post by Robert Munteanu
Hi Carsten,
Post by Carsten Ziegeler
Why is this release not following the normal release procedure and
available via the staging maven repo?
There are two main reasons.
1. While the build is driven by Maven, building Eclipse plug-ins with
Tycho means that some of the regular Maven plugins don't work. For
instance, the source and javadoc plugin, see [1],[2] . Since IIUC the
release is based on the source code, and the binaries are just for
convenience, I opted not to make the release run on the output of
individual projects, but on the whole source zip.
2. If I were to deploy the plug-ins by themselves to the repo, it
would not be trivial to assemble back an p2/Eclipse update which can
be used to test the functionality of the release.
That being said, I'd be more than happy to refine this process, so
suggestions on how to do that are welcome :-)
Thanks,
Robert
[1]: https://dev.eclipse.org/mhonarc/lists/tycho-user/msg05730.html
[2]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=398061
Post by Carsten Ziegeler
Carsten
Post by Robert Munteanu
Anyone?
Robert
Post by Robert Munteanu
Hi,
https://issues.apache.org/jira/browse/SLING/fixforversion/12324873
https://issues.apache.org/jira/browse/SLING/component/12320908
The release candidate has been uploaded at
https://dist.apache.org/repos/dist/dev/sling,
and can be built using
mvn clean package
The resulting binaries can be installed into an Eclipse instance by
installing from the update site which is found at
p2update/target/repository after building the project.
[ ] +1 Approve the release
[ ] 0 Don't care
[ ] -1 Don't release, because ...
This majority vote is open for at least 72 hours.
--
Carsten Ziegeler
Adobe Research Switzerland
--
Carsten Ziegeler
Adobe Research Switzerland
--
Sent from my (old) computer
Robert Munteanu
2014-06-30 16:14:39 UTC
Permalink
I think I've gotten the right Maven/Tycho incantations set up and
deployed the 1.0.0 artifacts to

https://repository.apache.org/content/repositories/orgapachesling-1072/

The single compromise that I had to make is that the integration tests
were not included in the reactor build and therefore not deployed to
the nexus repo. Hopefully that's acceptable for the release.

I can restart the release vote if needed ( third time's the charm? )
but it would be good to know that I got things right this time.

Note: check_staged_release.sh took about 30 minutes to complete for me.

Thanks,

Robert
Post by Carsten Ziegeler
Thanks for the info, Robert - I'm not sure what the best approach is,
however the zip now contains 1.0.0-SNAPSHOT as versions but I guess the
final release should be 1.0.0. This would mean we're voting on something
which is then not released. On the other hand, if we put up 1.0.0 in a
globally available space everyone can simply download it from there and
voting, especially withdrawing the release is way harder.
Carsten
Post by Robert Munteanu
Hi Carsten,
Post by Carsten Ziegeler
Why is this release not following the normal release procedure and
available via the staging maven repo?
There are two main reasons.
1. While the build is driven by Maven, building Eclipse plug-ins with
Tycho means that some of the regular Maven plugins don't work. For
instance, the source and javadoc plugin, see [1],[2] . Since IIUC the
release is based on the source code, and the binaries are just for
convenience, I opted not to make the release run on the output of
individual projects, but on the whole source zip.
2. If I were to deploy the plug-ins by themselves to the repo, it
would not be trivial to assemble back an p2/Eclipse update which can
be used to test the functionality of the release.
That being said, I'd be more than happy to refine this process, so
suggestions on how to do that are welcome :-)
Thanks,
Robert
[1]: https://dev.eclipse.org/mhonarc/lists/tycho-user/msg05730.html
[2]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=398061
Post by Carsten Ziegeler
Carsten
Post by Robert Munteanu
Anyone?
Robert
Post by Robert Munteanu
Hi,
https://issues.apache.org/jira/browse/SLING/fixforversion/12324873
https://issues.apache.org/jira/browse/SLING/component/12320908
The release candidate has been uploaded at
https://dist.apache.org/repos/dist/dev/sling,
and can be built using
mvn clean package
The resulting binaries can be installed into an Eclipse instance by
installing from the update site which is found at
p2update/target/repository after building the project.
[ ] +1 Approve the release
[ ] 0 Don't care
[ ] -1 Don't release, because ...
This majority vote is open for at least 72 hours.
--
Carsten Ziegeler
Adobe Research Switzerland
--
Carsten Ziegeler
Adobe Research Switzerland
--
Sent from my (old) computer
Justin Edelson
2014-07-01 00:01:52 UTC
Permalink
+1
Post by Robert Munteanu
I think I've gotten the right Maven/Tycho incantations set up and
deployed the 1.0.0 artifacts to
https://repository.apache.org/content/repositories/orgapachesling-1072/
The single compromise that I had to make is that the integration tests
were not included in the reactor build and therefore not deployed to
the nexus repo. Hopefully that's acceptable for the release.
I can restart the release vote if needed ( third time's the charm? )
but it would be good to know that I got things right this time.
Note: check_staged_release.sh took about 30 minutes to complete for me.
Thanks,
Robert
Post by Carsten Ziegeler
Thanks for the info, Robert - I'm not sure what the best approach is,
however the zip now contains 1.0.0-SNAPSHOT as versions but I guess the
final release should be 1.0.0. This would mean we're voting on something
which is then not released. On the other hand, if we put up 1.0.0 in a
globally available space everyone can simply download it from there and
voting, especially withdrawing the release is way harder.
Carsten
Post by Robert Munteanu
Hi Carsten,
Post by Carsten Ziegeler
Why is this release not following the normal release procedure and
available via the staging maven repo?
There are two main reasons.
1. While the build is driven by Maven, building Eclipse plug-ins with
Tycho means that some of the regular Maven plugins don't work. For
instance, the source and javadoc plugin, see [1],[2] . Since IIUC the
release is based on the source code, and the binaries are just for
convenience, I opted not to make the release run on the output of
individual projects, but on the whole source zip.
2. If I were to deploy the plug-ins by themselves to the repo, it
would not be trivial to assemble back an p2/Eclipse update which can
be used to test the functionality of the release.
That being said, I'd be more than happy to refine this process, so
suggestions on how to do that are welcome :-)
Thanks,
Robert
[1]: https://dev.eclipse.org/mhonarc/lists/tycho-user/msg05730.html
[2]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=398061
Post by Carsten Ziegeler
Carsten
Post by Robert Munteanu
Anyone?
Robert
Post by Robert Munteanu
Hi,
https://issues.apache.org/jira/browse/SLING/fixforversion/12324873
https://issues.apache.org/jira/browse/SLING/component/12320908
The release candidate has been uploaded at
https://dist.apache.org/repos/dist/dev/sling,
and can be built using
mvn clean package
The resulting binaries can be installed into an Eclipse instance by
installing from the update site which is found at
p2update/target/repository after building the project.
[ ] +1 Approve the release
[ ] 0 Don't care
[ ] -1 Don't release, because ...
This majority vote is open for at least 72 hours.
--
Carsten Ziegeler
Adobe Research Switzerland
--
Carsten Ziegeler
Adobe Research Switzerland
--
Sent from my (old) computer
Carsten Ziegeler
2014-07-01 06:34:03 UTC
Permalink
Thanks for redoing, Robert.

+1

Carsten
Post by Robert Munteanu
+1
Post by Robert Munteanu
I think I've gotten the right Maven/Tycho incantations set up and
deployed the 1.0.0 artifacts to
https://repository.apache.org/content/repositories/orgapachesling-1072/
Post by Robert Munteanu
The single compromise that I had to make is that the integration tests
were not included in the reactor build and therefore not deployed to
the nexus repo. Hopefully that's acceptable for the release.
I can restart the release vote if needed ( third time's the charm? )
but it would be good to know that I got things right this time.
Note: check_staged_release.sh took about 30 minutes to complete for me.
Thanks,
Robert
Post by Carsten Ziegeler
Thanks for the info, Robert - I'm not sure what the best approach is,
however the zip now contains 1.0.0-SNAPSHOT as versions but I guess the
final release should be 1.0.0. This would mean we're voting on something
which is then not released. On the other hand, if we put up 1.0.0 in a
globally available space everyone can simply download it from there and
voting, especially withdrawing the release is way harder.
Carsten
Post by Robert Munteanu
Hi Carsten,
On Mon, Jun 30, 2014 at 8:57 AM, Carsten Ziegeler <
Post by Carsten Ziegeler
Why is this release not following the normal release procedure and
available via the staging maven repo?
There are two main reasons.
1. While the build is driven by Maven, building Eclipse plug-ins with
Tycho means that some of the regular Maven plugins don't work. For
instance, the source and javadoc plugin, see [1],[2] . Since IIUC the
release is based on the source code, and the binaries are just for
convenience, I opted not to make the release run on the output of
individual projects, but on the whole source zip.
2. If I were to deploy the plug-ins by themselves to the repo, it
would not be trivial to assemble back an p2/Eclipse update which can
be used to test the functionality of the release.
That being said, I'd be more than happy to refine this process, so
suggestions on how to do that are welcome :-)
Thanks,
Robert
[1]: https://dev.eclipse.org/mhonarc/lists/tycho-user/msg05730.html
[2]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=398061
Post by Carsten Ziegeler
Carsten
Post by Robert Munteanu
Anyone?
Robert
On Thu, Jun 26, 2014 at 11:32 AM, Robert Munteanu <
Post by Robert Munteanu
Hi,
https://issues.apache.org/jira/browse/SLING/fixforversion/12324873
Post by Robert Munteanu
Post by Carsten Ziegeler
Post by Robert Munteanu
Post by Carsten Ziegeler
Post by Robert Munteanu
Post by Robert Munteanu
https://issues.apache.org/jira/browse/SLING/component/12320908
The release candidate has been uploaded at
https://dist.apache.org/repos/dist/dev/sling,
and can be built using
mvn clean package
The resulting binaries can be installed into an Eclipse instance
by
Post by Robert Munteanu
Post by Carsten Ziegeler
Post by Robert Munteanu
Post by Carsten Ziegeler
Post by Robert Munteanu
Post by Robert Munteanu
installing from the update site which is found at
p2update/target/repository after building the project.
[ ] +1 Approve the release
[ ] 0 Don't care
[ ] -1 Don't release, because ...
This majority vote is open for at least 72 hours.
--
Carsten Ziegeler
Adobe Research Switzerland
--
Carsten Ziegeler
Adobe Research Switzerland
--
Sent from my (old) computer
--
Carsten Ziegeler
Adobe Research Switzerland
cziegeler-1oDqGaOF3Lkdnm+***@public.gmane.org
Stefan Egli
2014-07-01 09:55:21 UTC
Permalink
+1
(verified md5 & sha1 using the check_staged_release.sh)

Cheers,
Stefan
Post by Carsten Ziegeler
Thanks for redoing, Robert.
+1
Carsten
Post by Robert Munteanu
+1
Post by Robert Munteanu
I think I've gotten the right Maven/Tycho incantations set up and
deployed the 1.0.0 artifacts to
https://repository.apache.org/content/repositories/orgapachesling-1072/
Post by Robert Munteanu
The single compromise that I had to make is that the integration tests
were not included in the reactor build and therefore not deployed to
the nexus repo. Hopefully that's acceptable for the release.
I can restart the release vote if needed ( third time's the charm? )
but it would be good to know that I got things right this time.
Note: check_staged_release.sh took about 30 minutes to complete for
me.
Post by Robert Munteanu
Thanks,
Robert
On Mon, Jun 30, 2014 at 1:53 PM, Carsten Ziegeler
Post by Carsten Ziegeler
Thanks for the info, Robert - I'm not sure what the best approach is,
however the zip now contains 1.0.0-SNAPSHOT as versions but I guess
the
Post by Robert Munteanu
Post by Carsten Ziegeler
final release should be 1.0.0. This would mean we're voting on
something
Post by Robert Munteanu
Post by Carsten Ziegeler
which is then not released. On the other hand, if we put up 1.0.0 in
a
Post by Robert Munteanu
Post by Carsten Ziegeler
globally available space everyone can simply download it from there
and
Post by Robert Munteanu
Post by Carsten Ziegeler
voting, especially withdrawing the release is way harder.
Carsten
Post by Robert Munteanu
Hi Carsten,
On Mon, Jun 30, 2014 at 8:57 AM, Carsten Ziegeler <
Post by Carsten Ziegeler
Why is this release not following the normal release procedure and
available via the staging maven repo?
There are two main reasons.
1. While the build is driven by Maven, building Eclipse plug-ins
with
Post by Robert Munteanu
Post by Carsten Ziegeler
Post by Robert Munteanu
Tycho means that some of the regular Maven plugins don't work. For
instance, the source and javadoc plugin, see [1],[2] . Since IIUC
the
Post by Robert Munteanu
Post by Carsten Ziegeler
Post by Robert Munteanu
release is based on the source code, and the binaries are just for
convenience, I opted not to make the release run on the output of
individual projects, but on the whole source zip.
2. If I were to deploy the plug-ins by themselves to the repo, it
would not be trivial to assemble back an p2/Eclipse update which can
be used to test the functionality of the release.
That being said, I'd be more than happy to refine this process, so
suggestions on how to do that are welcome :-)
Thanks,
Robert
[1]: https://dev.eclipse.org/mhonarc/lists/tycho-user/msg05730.html
[2]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=398061
Post by Carsten Ziegeler
Carsten
Post by Robert Munteanu
Anyone?
Robert
On Thu, Jun 26, 2014 at 11:32 AM, Robert Munteanu <
Post by Robert Munteanu
Hi,
https://issues.apache.org/jira/browse/SLING/fixforversion/12324873
Post by Robert Munteanu
Post by Carsten Ziegeler
Post by Robert Munteanu
Post by Carsten Ziegeler
Post by Robert Munteanu
Post by Robert Munteanu
https://issues.apache.org/jira/browse/SLING/component/12320908
The release candidate has been uploaded at
https://dist.apache.org/repos/dist/dev/sling,
and can be built using
mvn clean package
The resulting binaries can be installed into an Eclipse
instance
by
Post by Robert Munteanu
Post by Carsten Ziegeler
Post by Robert Munteanu
Post by Carsten Ziegeler
Post by Robert Munteanu
Post by Robert Munteanu
installing from the update site which is found at
p2update/target/repository after building the project.
[ ] +1 Approve the release
[ ] 0 Don't care
[ ] -1 Don't release, because ...
This majority vote is open for at least 72 hours.
--
Carsten Ziegeler
Adobe Research Switzerland
--
Carsten Ziegeler
Adobe Research Switzerland
--
Sent from my (old) computer
--
Carsten Ziegeler
Adobe Research Switzerland
Daniel Klco
2014-07-01 12:20:47 UTC
Permalink
+1
Post by Stefan Egli
+1
(verified md5 & sha1 using the check_staged_release.sh)
Cheers,
Stefan
Post by Carsten Ziegeler
Thanks for redoing, Robert.
+1
Carsten
Post by Robert Munteanu
+1
Post by Robert Munteanu
I think I've gotten the right Maven/Tycho incantations set up and
deployed the 1.0.0 artifacts to
https://repository.apache.org/content/repositories/orgapachesling-1072/
Post by Robert Munteanu
The single compromise that I had to make is that the integration tests
were not included in the reactor build and therefore not deployed to
the nexus repo. Hopefully that's acceptable for the release.
I can restart the release vote if needed ( third time's the charm? )
but it would be good to know that I got things right this time.
Note: check_staged_release.sh took about 30 minutes to complete for
me.
Post by Robert Munteanu
Thanks,
Robert
On Mon, Jun 30, 2014 at 1:53 PM, Carsten Ziegeler
Post by Carsten Ziegeler
Thanks for the info, Robert - I'm not sure what the best approach is,
however the zip now contains 1.0.0-SNAPSHOT as versions but I guess
the
Post by Robert Munteanu
Post by Carsten Ziegeler
final release should be 1.0.0. This would mean we're voting on
something
Post by Robert Munteanu
Post by Carsten Ziegeler
which is then not released. On the other hand, if we put up 1.0.0 in
a
Post by Robert Munteanu
Post by Carsten Ziegeler
globally available space everyone can simply download it from there
and
Post by Robert Munteanu
Post by Carsten Ziegeler
voting, especially withdrawing the release is way harder.
Carsten
Post by Robert Munteanu
Hi Carsten,
On Mon, Jun 30, 2014 at 8:57 AM, Carsten Ziegeler <
Post by Carsten Ziegeler
Why is this release not following the normal release procedure and
available via the staging maven repo?
There are two main reasons.
1. While the build is driven by Maven, building Eclipse plug-ins
with
Post by Robert Munteanu
Post by Carsten Ziegeler
Post by Robert Munteanu
Tycho means that some of the regular Maven plugins don't work. For
instance, the source and javadoc plugin, see [1],[2] . Since IIUC
the
Post by Robert Munteanu
Post by Carsten Ziegeler
Post by Robert Munteanu
release is based on the source code, and the binaries are just for
convenience, I opted not to make the release run on the output of
individual projects, but on the whole source zip.
2. If I were to deploy the plug-ins by themselves to the repo, it
would not be trivial to assemble back an p2/Eclipse update which can
be used to test the functionality of the release.
That being said, I'd be more than happy to refine this process, so
suggestions on how to do that are welcome :-)
Thanks,
Robert
[1]: https://dev.eclipse.org/mhonarc/lists/tycho-user/msg05730.html
[2]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=398061
Post by Carsten Ziegeler
Carsten
Post by Robert Munteanu
Anyone?
Robert
On Thu, Jun 26, 2014 at 11:32 AM, Robert Munteanu <
Post by Robert Munteanu
Hi,
https://issues.apache.org/jira/browse/SLING/fixforversion/12324873
Post by Robert Munteanu
Post by Carsten Ziegeler
Post by Robert Munteanu
Post by Carsten Ziegeler
Post by Robert Munteanu
Post by Robert Munteanu
https://issues.apache.org/jira/browse/SLING/component/12320908
The release candidate has been uploaded at
https://dist.apache.org/repos/dist/dev/sling,
and can be built using
mvn clean package
The resulting binaries can be installed into an Eclipse
instance
by
Post by Robert Munteanu
Post by Carsten Ziegeler
Post by Robert Munteanu
Post by Carsten Ziegeler
Post by Robert Munteanu
Post by Robert Munteanu
installing from the update site which is found at
p2update/target/repository after building the project.
[ ] +1 Approve the release
[ ] 0 Don't care
[ ] -1 Don't release, because ...
This majority vote is open for at least 72 hours.
--
Carsten Ziegeler
Adobe Research Switzerland
--
Carsten Ziegeler
Adobe Research Switzerland
--
Sent from my (old) computer
--
Carsten Ziegeler
Adobe Research Switzerland
Robert Munteanu
2014-07-01 12:34:21 UTC
Permalink
Hi,

The vote has passed with the following result :

+1 (binding): Robert Munteanu, Justin Edelson, Carsten Ziegler, Stefan
Egli, Daniel Klco

I will copy this release to the Sling dist directory and promote the
artifacts to the central Maven repository.

Robert

Loading...