You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Alex Karasulu <ak...@apache.org> on 2011/02/07 18:03:59 UTC
[Shared] Release plan for 1.0-m1
Hi all,
Now with this check pointed merge back to trunks which is about to happen in
15-20 minutes after some super clean, build, test, run of studio etc, we can
release shared 1.0-m1 if y'all like. Here's a release plan that Pierre and I
discussed:
(0) confirm a stable build in trunk with merge
(1) commit merge back to trunk
(2) assign release manager
(3) modify pom's for new 1.0-m1 version
(4) confirm stability
(5) tag, kick off vote
(6) if vote passes, release
(7) merge back trunk changes with 1.0-m2-SNAPSHOT version into m1
(8) rename m1 branches to m2
In the meantime right after step #1 we can still continue work on stage II
in the m1 branch.
Thoughts?
<my-personal-opinion>
I think we're progressing so rapidly in shared that we might be done and
ready for M1 with all features here in less than 7-10 days. There may be no
point to have more than one milestone release (we can goto RC1 right after
M1) and if this is the case maybe we should push all into M1 in about 7-10
days. This might save our release manager some effort.
Also shared-ldap is messy now. I purified the codec code, and the model,
then moved it out. If you look into the ldap-model and the ldap-codec
modules you'll see that it's much cleaner dependency wise. If you look at
shared-ldap it will look almost empty with what seems a poor organization of
incoherent pieces that remained. This is because what is left here is the
sludge, the toxins, that were extracted from the purified model and codec.
We still need to move these out and make it so the shared-ldap module is
empty.
Then we need to make shared ldap into a consolidation jar just like
shared-all but with ONLY what is needed to run as the standard LDAP client
jar. All a user will need is shared-ldap and they have all they need to
connect and go with any ldap server. The shared-ldap module will pull in the
following packages plus dependencies:
shared-ldap-model
shared-ldap-codec
shared-ldap-asn1-api
shared-ldap-asn1-ber
shared-util
shared-i18n
mina dependencies
commons dependencies
The shared-ldap jar should be the only jar anyone needs to connect and go
with an LDAP server. The API documentation generated from it, the javadocs
will be the ldap API product. We will also have some extras plugin
jars/bundles as optional pieces for ADS specific functionality.
Regardless of the technical points, I think it's still harmless to release
an m1 in its present condition. However I don't think it's very useful with
the status of shared-ldap as it is now. If I don't have to stop working in
the m1 branch (to be renamed m2 after step #1 above) and someone other than
myself wants to deal with being the release manager then they're welcome to
release. I'll cast a +0 on a release vote if all the legal aspects of the
release are in order.
</my-personal-opinion>
Regards,
Alex
Re: [Shared] Release plan for 1.0-m1
Posted by Emmanuel Lecharny <el...@gmail.com>.
On 2/7/11 10:49 PM, Stefan Seelmann wrote:
> On Mon, Feb 7, 2011 at 6:03 PM, Alex Karasulu<ak...@apache.org> wrote:
>> Hi all,
>> Now with this check pointed merge back to trunks which is about to happen in
>> 15-20 minutes after some super clean, build, test, run of studio etc, we can
>> release shared 1.0-m1 if y'all like. Here's a release plan that Pierre and I
>> discussed:
>> (0) confirm a stable build in trunk with merge
>> (1) commit merge back to trunk
>> (2) assign release manager
>> (3) modify pom's for new 1.0-m1 version
>> (4) confirm stability
>> (5) tag, kick off vote
>> (6) if vote passes, release
>> (7) merge back trunk changes with 1.0-m2-SNAPSHOT version into m1
>> (8) rename m1 branches to m2
>> In the meantime right after step #1 we can still continue work on stage II
>> in the m1 branch.
> Before a shared release we need to release three other artifactes:
> - project: with updated plugin versions
> - checkstyle-configuration: currently a snapshot is used
> - junit-addons: currently a snapshot is used
>
> So let's start with them, then we'll see the progress of the m1 branch.
I just updated project/pom.xml with the latest plugin's version
(surefire and antlr).
Feel free to relese project whenever you want to.
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
Re: [Shared] Release plan for 1.0-m1
Posted by Alex Karasulu <ak...@apache.org>.
On Mon, Feb 7, 2011 at 11:49 PM, Stefan Seelmann <se...@apache.org> wrote:
> On Mon, Feb 7, 2011 at 6:03 PM, Alex Karasulu <ak...@apache.org> wrote:
>> Hi all,
>> Now with this check pointed merge back to trunks which is about to happen in
>> 15-20 minutes after some super clean, build, test, run of studio etc, we can
>> release shared 1.0-m1 if y'all like. Here's a release plan that Pierre and I
>> discussed:
>> (0) confirm a stable build in trunk with merge
>> (1) commit merge back to trunk
>> (2) assign release manager
>> (3) modify pom's for new 1.0-m1 version
>> (4) confirm stability
>> (5) tag, kick off vote
>> (6) if vote passes, release
>> (7) merge back trunk changes with 1.0-m2-SNAPSHOT version into m1
>> (8) rename m1 branches to m2
>> In the meantime right after step #1 we can still continue work on stage II
>> in the m1 branch.
>
> Before a shared release we need to release three other artifactes:
> - project: with updated plugin versions
> - checkstyle-configuration: currently a snapshot is used
> - junit-addons: currently a snapshot is used
>
> So let's start with them, then we'll see the progress of the m1 branch.
Fine by me. Gives us more time to work on m1.
Regards,
Alex
Re: [Shared] Release plan for 1.0-m1
Posted by Stefan Seelmann <se...@apache.org>.
On Tue, Feb 8, 2011 at 12:41 PM, Emmanuel Lécharny <el...@apache.org> wrote:
> On 2/8/11 12:37 PM, Stefan Seelmann wrote:
>>
>> On Tue, Feb 8, 2011 at 12:20 PM, Emmanuel Lecharny<el...@gmail.com>
>> wrote:
>>>
>>> On 2/7/11 10:49 PM, Stefan Seelmann wrote:
>>>>
>>>> On Mon, Feb 7, 2011 at 6:03 PM, Alex Karasulu<ak...@apache.org>
>>>> wrote:
>>>>>
>>>>> Hi all,
>>>>> Now with this check pointed merge back to trunks which is about to
>>>>> happen
>>>>> in
>>>>> 15-20 minutes after some super clean, build, test, run of studio etc,
>>>>> we
>>>>> can
>>>>> release shared 1.0-m1 if y'all like. Here's a release plan that Pierre
>>>>> and I
>>>>> discussed:
>>>>> (0) confirm a stable build in trunk with merge
>>>>> (1) commit merge back to trunk
>>>>> (2) assign release manager
>>>>> (3) modify pom's for new 1.0-m1 version
>>>>> (4) confirm stability
>>>>> (5) tag, kick off vote
>>>>> (6) if vote passes, release
>>>>> (7) merge back trunk changes with 1.0-m2-SNAPSHOT version into m1
>>>>> (8) rename m1 branches to m2
>>>>> In the meantime right after step #1 we can still continue work on stage
>>>>> II
>>>>> in the m1 branch.
>>>>
>>>> Before a shared release we need to release three other artifactes:
>>>> - project: with updated plugin versions
>>>> - checkstyle-configuration: currently a snapshot is used
>>>> - junit-addons: currently a snapshot is used
>>>>
>>>> So let's start with them, then we'll see the progress of the m1 branch.
>>>
>>> Correction : I updated the following plugins :
>>> maven-changes-plugin and maven-ear-plugin
>>
>> Thanks. There is also a new version 2.3.4 of the Felix
>> maven-bundle-plugin, I'll update that too, test the build, and start
>> the release.
>
> One more plugin to update :
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building ApacheDS Manuals 1.5.8-SNAPSHOT
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> [INFO] --- versions-maven-plugin:1.2:display-plugin-updates (default-cli) @
> manuals ---
> [INFO]
> [INFO] All plugins with a version specified are using the latest versions.
> [INFO]
> [WARNING] The following plugins do not have their version specified:
> [WARNING] com.agilejava.docbkx:docbkx-maven-plugin ...............
> (unknown)
This is already defined in project 20-SNAPSHOT, so once released that
will be ok.
Re: [Shared] Release plan for 1.0-m1
Posted by Emmanuel Lecharny <el...@gmail.com>.
On 2/8/11 12:41 PM, Emmanuel Lécharny wrote:
> On 2/8/11 12:37 PM, Stefan Seelmann wrote:
>> On Tue, Feb 8, 2011 at 12:20 PM, Emmanuel
>> Lecharny<el...@gmail.com> wrote:
>>> On 2/7/11 10:49 PM, Stefan Seelmann wrote:
>>>> On Mon, Feb 7, 2011 at 6:03 PM, Alex Karasulu<ak...@apache.org>
>>>> wrote:
>>>>> Hi all,
>>>>> Now with this check pointed merge back to trunks which is about to
>>>>> happen
>>>>> in
>>>>> 15-20 minutes after some super clean, build, test, run of studio
>>>>> etc, we
>>>>> can
>>>>> release shared 1.0-m1 if y'all like. Here's a release plan that
>>>>> Pierre
>>>>> and I
>>>>> discussed:
>>>>> (0) confirm a stable build in trunk with merge
>>>>> (1) commit merge back to trunk
>>>>> (2) assign release manager
>>>>> (3) modify pom's for new 1.0-m1 version
>>>>> (4) confirm stability
>>>>> (5) tag, kick off vote
>>>>> (6) if vote passes, release
>>>>> (7) merge back trunk changes with 1.0-m2-SNAPSHOT version into m1
>>>>> (8) rename m1 branches to m2
>>>>> In the meantime right after step #1 we can still continue work on
>>>>> stage
>>>>> II
>>>>> in the m1 branch.
>>>> Before a shared release we need to release three other artifactes:
>>>> - project: with updated plugin versions
>>>> - checkstyle-configuration: currently a snapshot is used
>>>> - junit-addons: currently a snapshot is used
>>>>
>>>> So let's start with them, then we'll see the progress of the m1
>>>> branch.
>>> Correction : I updated the following plugins :
>>> maven-changes-plugin and maven-ear-plugin
>> Thanks. There is also a new version 2.3.4 of the Felix
>> maven-bundle-plugin, I'll update that too, test the build, and start
>> the release.
>
> One more plugin to update :
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building ApacheDS Manuals 1.5.8-SNAPSHOT
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> [INFO] --- versions-maven-plugin:1.2:display-plugin-updates
> (default-cli) @ manuals ---
> [INFO]
> [INFO] All plugins with a version specified are using the latest
> versions.
> [INFO]
> [WARNING] The following plugins do not have their version specified:
> [WARNING] com.agilejava.docbkx:docbkx-maven-plugin ...............
> (unknown)
>
>
I just checked all the jars, in shared, we are up to date for all of them.
I have to update some of the apacheds jars, but it's orthogonal to M1 :
[INFO] The following dependencies in Dependency Management have newer
versions:
[INFO] dnsjava:dnsjava ....................................... 2.0.1
-> 2.1.0
[INFO] net.sf.ehcache:ehcache-core ........................... 2.2.0
-> 2.3.2
[INFO] opensymphony:quartz ................................... 1.6.0
-> 1.6.3
[INFO] org.apache.ant:ant .................................... 1.8.1
-> 1.8.2
[INFO] org.apache.derby:derby .......................... 10.4.2.0 ->
10.7.1.1
[INFO] org.apache.maven:maven-archiver ......................... 2.2
-> 2.4.1
[INFO] org.apache.maven:maven-artifact ....................... 2.2.1
-> 3.0.2
[INFO] org.apache.maven:maven-plugin-api ..................... 2.2.1
-> 3.0.2
[INFO] org.apache.maven:maven-project .................. 2.0.9 ->
3.0-alpha-2
[INFO] org.apache.velocity:velocity ........................ 1.5 ->
1.7-beta1
[INFO] org.mortbay.jetty:jetty ............................. 6.1.14 ->
6.1.26
[INFO] org.mortbay.jetty:jetty-util ........................ 6.1.14 ->
6.1.26
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
Re: [Shared] Release plan for 1.0-m1
Posted by Emmanuel Lécharny <el...@apache.org>.
On 2/8/11 12:37 PM, Stefan Seelmann wrote:
> On Tue, Feb 8, 2011 at 12:20 PM, Emmanuel Lecharny<el...@gmail.com> wrote:
>> On 2/7/11 10:49 PM, Stefan Seelmann wrote:
>>> On Mon, Feb 7, 2011 at 6:03 PM, Alex Karasulu<ak...@apache.org>
>>> wrote:
>>>> Hi all,
>>>> Now with this check pointed merge back to trunks which is about to happen
>>>> in
>>>> 15-20 minutes after some super clean, build, test, run of studio etc, we
>>>> can
>>>> release shared 1.0-m1 if y'all like. Here's a release plan that Pierre
>>>> and I
>>>> discussed:
>>>> (0) confirm a stable build in trunk with merge
>>>> (1) commit merge back to trunk
>>>> (2) assign release manager
>>>> (3) modify pom's for new 1.0-m1 version
>>>> (4) confirm stability
>>>> (5) tag, kick off vote
>>>> (6) if vote passes, release
>>>> (7) merge back trunk changes with 1.0-m2-SNAPSHOT version into m1
>>>> (8) rename m1 branches to m2
>>>> In the meantime right after step #1 we can still continue work on stage
>>>> II
>>>> in the m1 branch.
>>> Before a shared release we need to release three other artifactes:
>>> - project: with updated plugin versions
>>> - checkstyle-configuration: currently a snapshot is used
>>> - junit-addons: currently a snapshot is used
>>>
>>> So let's start with them, then we'll see the progress of the m1 branch.
>> Correction : I updated the following plugins :
>> maven-changes-plugin and maven-ear-plugin
> Thanks. There is also a new version 2.3.4 of the Felix
> maven-bundle-plugin, I'll update that too, test the build, and start
> the release.
One more plugin to update :
[INFO]
------------------------------------------------------------------------
[INFO] Building ApacheDS Manuals 1.5.8-SNAPSHOT
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- versions-maven-plugin:1.2:display-plugin-updates
(default-cli) @ manuals ---
[INFO]
[INFO] All plugins with a version specified are using the latest versions.
[INFO]
[WARNING] The following plugins do not have their version specified:
[WARNING] com.agilejava.docbkx:docbkx-maven-plugin ...............
(unknown)
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
Re: [Shared] Release plan for 1.0-m1
Posted by Stefan Seelmann <se...@apache.org>.
On Tue, Feb 8, 2011 at 12:42 PM, Pierre-Arnaud Marcelot <pa...@marcelot.net> wrote:
> Hi guys,
>
> I'm not sure the current branch is ready for a release today, looking at Alex's first mail in this thread:
>> On 7 févr. 2011, at 18:03, Alex Karasulu wrote:
>>> I think we're progressing so rapidly in shared that we might be done and ready for M1 with all features here in less than 7-10 days.
>
> Especially with the new introduction of Felix into Shared.
If at all we are going to release the current trunk.
Kind Regards,
Stefan
Re: [Shared] Release plan for 1.0-m1
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Hi guys,
I'm not sure the current branch is ready for a release today, looking at Alex's first mail in this thread:
> On 7 févr. 2011, at 18:03, Alex Karasulu wrote:
>> I think we're progressing so rapidly in shared that we might be done and ready for M1 with all features here in less than 7-10 days.
Especially with the new introduction of Felix into Shared.
Regards,
Pierre-Arnaud
On 8 févr. 2011, at 12:37, Stefan Seelmann wrote:
> On Tue, Feb 8, 2011 at 12:20 PM, Emmanuel Lecharny <el...@gmail.com> wrote:
>> On 2/7/11 10:49 PM, Stefan Seelmann wrote:
>>>
>>> On Mon, Feb 7, 2011 at 6:03 PM, Alex Karasulu<ak...@apache.org>
>>> wrote:
>>>>
>>>> Hi all,
>>>> Now with this check pointed merge back to trunks which is about to happen
>>>> in
>>>> 15-20 minutes after some super clean, build, test, run of studio etc, we
>>>> can
>>>> release shared 1.0-m1 if y'all like. Here's a release plan that Pierre
>>>> and I
>>>> discussed:
>>>> (0) confirm a stable build in trunk with merge
>>>> (1) commit merge back to trunk
>>>> (2) assign release manager
>>>> (3) modify pom's for new 1.0-m1 version
>>>> (4) confirm stability
>>>> (5) tag, kick off vote
>>>> (6) if vote passes, release
>>>> (7) merge back trunk changes with 1.0-m2-SNAPSHOT version into m1
>>>> (8) rename m1 branches to m2
>>>> In the meantime right after step #1 we can still continue work on stage
>>>> II
>>>> in the m1 branch.
>>>
>>> Before a shared release we need to release three other artifactes:
>>> - project: with updated plugin versions
>>> - checkstyle-configuration: currently a snapshot is used
>>> - junit-addons: currently a snapshot is used
>>>
>>> So let's start with them, then we'll see the progress of the m1 branch.
>>
>> Correction : I updated the following plugins :
>> maven-changes-plugin and maven-ear-plugin
>
> Thanks. There is also a new version 2.3.4 of the Felix
> maven-bundle-plugin, I'll update that too, test the build, and start
> the release.
>
> Kind Regards,
> Stefan
Re: [Shared] Release plan for 1.0-m1
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Ok, thanks for the update.
Then, it should work... :(
Regards,
Pierre-Arnaud
On 8 févr. 2011, at 13:25, Stefan Seelmann wrote:
>> Have you tested this on trunk or the m1 branch ?
>
> On trunk.
>
> In project/pom.xml I set version 2.3.4.
> In studio/pom.xml I used project:20-SNAPSHOT
Re: [Shared] Release plan for 1.0-m1
Posted by Stefan Seelmann <se...@apache.org>.
> Have you tested this on trunk or the m1 branch ?
On trunk.
In project/pom.xml I set version 2.3.4.
In studio/pom.xml I used project:20-SNAPSHOT
Re: [Shared] Release plan for 1.0-m1
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Hi Stefan,
Have you tested this on trunk or the m1 branch ?
Regards,
Pierre-Arnaud
On 8 févr. 2011, at 13:19, Stefan Seelmann wrote:
> On Tue, Feb 8, 2011 at 12:37 PM, Stefan Seelmann <se...@apache.org> wrote:
>> On Tue, Feb 8, 2011 at 12:20 PM, Emmanuel Lecharny <el...@gmail.com> wrote:
>>> On 2/7/11 10:49 PM, Stefan Seelmann wrote:
>>>>
>>>> On Mon, Feb 7, 2011 at 6:03 PM, Alex Karasulu<ak...@apache.org>
>>>> wrote:
>>>>>
>>>>> Hi all,
>>>>> Now with this check pointed merge back to trunks which is about to happen
>>>>> in
>>>>> 15-20 minutes after some super clean, build, test, run of studio etc, we
>>>>> can
>>>>> release shared 1.0-m1 if y'all like. Here's a release plan that Pierre
>>>>> and I
>>>>> discussed:
>>>>> (0) confirm a stable build in trunk with merge
>>>>> (1) commit merge back to trunk
>>>>> (2) assign release manager
>>>>> (3) modify pom's for new 1.0-m1 version
>>>>> (4) confirm stability
>>>>> (5) tag, kick off vote
>>>>> (6) if vote passes, release
>>>>> (7) merge back trunk changes with 1.0-m2-SNAPSHOT version into m1
>>>>> (8) rename m1 branches to m2
>>>>> In the meantime right after step #1 we can still continue work on stage
>>>>> II
>>>>> in the m1 branch.
>>>>
>>>> Before a shared release we need to release three other artifactes:
>>>> - project: with updated plugin versions
>>>> - checkstyle-configuration: currently a snapshot is used
>>>> - junit-addons: currently a snapshot is used
>>>>
>>>> So let's start with them, then we'll see the progress of the m1 branch.
>>>
>>> Correction : I updated the following plugins :
>>> maven-changes-plugin and maven-ear-plugin
>>
>> Thanks. There is also a new version 2.3.4 of the Felix
>> maven-bundle-plugin, I'll update that too, test the build, and start
>> the release.
>
> Seems in Felix maven-bundle-plugin:2.3.4 some changes are not
> compatible with our setup. At least when starting the Studio
> application (current trunk) the LDAP perspective can't be loaded.
>
> I'd suggest we keep version 2.2 and investigate later, especially as
> lot of OSGi/Felix work is done in m1 branch.
>
> Kind Regards,
> Stefan
Re: [Shared] Release plan for 1.0-m1
Posted by Stefan Seelmann <se...@apache.org>.
On Tue, Feb 8, 2011 at 12:37 PM, Stefan Seelmann <se...@apache.org> wrote:
> On Tue, Feb 8, 2011 at 12:20 PM, Emmanuel Lecharny <el...@gmail.com> wrote:
>> On 2/7/11 10:49 PM, Stefan Seelmann wrote:
>>>
>>> On Mon, Feb 7, 2011 at 6:03 PM, Alex Karasulu<ak...@apache.org>
>>> wrote:
>>>>
>>>> Hi all,
>>>> Now with this check pointed merge back to trunks which is about to happen
>>>> in
>>>> 15-20 minutes after some super clean, build, test, run of studio etc, we
>>>> can
>>>> release shared 1.0-m1 if y'all like. Here's a release plan that Pierre
>>>> and I
>>>> discussed:
>>>> (0) confirm a stable build in trunk with merge
>>>> (1) commit merge back to trunk
>>>> (2) assign release manager
>>>> (3) modify pom's for new 1.0-m1 version
>>>> (4) confirm stability
>>>> (5) tag, kick off vote
>>>> (6) if vote passes, release
>>>> (7) merge back trunk changes with 1.0-m2-SNAPSHOT version into m1
>>>> (8) rename m1 branches to m2
>>>> In the meantime right after step #1 we can still continue work on stage
>>>> II
>>>> in the m1 branch.
>>>
>>> Before a shared release we need to release three other artifactes:
>>> - project: with updated plugin versions
>>> - checkstyle-configuration: currently a snapshot is used
>>> - junit-addons: currently a snapshot is used
>>>
>>> So let's start with them, then we'll see the progress of the m1 branch.
>>
>> Correction : I updated the following plugins :
>> maven-changes-plugin and maven-ear-plugin
>
> Thanks. There is also a new version 2.3.4 of the Felix
> maven-bundle-plugin, I'll update that too, test the build, and start
> the release.
Seems in Felix maven-bundle-plugin:2.3.4 some changes are not
compatible with our setup. At least when starting the Studio
application (current trunk) the LDAP perspective can't be loaded.
I'd suggest we keep version 2.2 and investigate later, especially as
lot of OSGi/Felix work is done in m1 branch.
Kind Regards,
Stefan
Re: [Shared] Release plan for 1.0-m1
Posted by Stefan Seelmann <se...@apache.org>.
On Tue, Feb 8, 2011 at 12:20 PM, Emmanuel Lecharny <el...@gmail.com> wrote:
> On 2/7/11 10:49 PM, Stefan Seelmann wrote:
>>
>> On Mon, Feb 7, 2011 at 6:03 PM, Alex Karasulu<ak...@apache.org>
>> wrote:
>>>
>>> Hi all,
>>> Now with this check pointed merge back to trunks which is about to happen
>>> in
>>> 15-20 minutes after some super clean, build, test, run of studio etc, we
>>> can
>>> release shared 1.0-m1 if y'all like. Here's a release plan that Pierre
>>> and I
>>> discussed:
>>> (0) confirm a stable build in trunk with merge
>>> (1) commit merge back to trunk
>>> (2) assign release manager
>>> (3) modify pom's for new 1.0-m1 version
>>> (4) confirm stability
>>> (5) tag, kick off vote
>>> (6) if vote passes, release
>>> (7) merge back trunk changes with 1.0-m2-SNAPSHOT version into m1
>>> (8) rename m1 branches to m2
>>> In the meantime right after step #1 we can still continue work on stage
>>> II
>>> in the m1 branch.
>>
>> Before a shared release we need to release three other artifactes:
>> - project: with updated plugin versions
>> - checkstyle-configuration: currently a snapshot is used
>> - junit-addons: currently a snapshot is used
>>
>> So let's start with them, then we'll see the progress of the m1 branch.
>
> Correction : I updated the following plugins :
> maven-changes-plugin and maven-ear-plugin
Thanks. There is also a new version 2.3.4 of the Felix
maven-bundle-plugin, I'll update that too, test the build, and start
the release.
Kind Regards,
Stefan
Re: [Shared] Release plan for 1.0-m1
Posted by Emmanuel Lecharny <el...@gmail.com>.
On 2/7/11 10:49 PM, Stefan Seelmann wrote:
> On Mon, Feb 7, 2011 at 6:03 PM, Alex Karasulu<ak...@apache.org> wrote:
>> Hi all,
>> Now with this check pointed merge back to trunks which is about to happen in
>> 15-20 minutes after some super clean, build, test, run of studio etc, we can
>> release shared 1.0-m1 if y'all like. Here's a release plan that Pierre and I
>> discussed:
>> (0) confirm a stable build in trunk with merge
>> (1) commit merge back to trunk
>> (2) assign release manager
>> (3) modify pom's for new 1.0-m1 version
>> (4) confirm stability
>> (5) tag, kick off vote
>> (6) if vote passes, release
>> (7) merge back trunk changes with 1.0-m2-SNAPSHOT version into m1
>> (8) rename m1 branches to m2
>> In the meantime right after step #1 we can still continue work on stage II
>> in the m1 branch.
> Before a shared release we need to release three other artifactes:
> - project: with updated plugin versions
> - checkstyle-configuration: currently a snapshot is used
> - junit-addons: currently a snapshot is used
>
> So let's start with them, then we'll see the progress of the m1 branch.
Correction : I updated the following plugins :
maven-changes-plugin and maven-ear-plugin
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
Re: [Shared] Release plan for 1.0-m1
Posted by Stefan Seelmann <se...@apache.org>.
On Mon, Feb 7, 2011 at 6:03 PM, Alex Karasulu <ak...@apache.org> wrote:
> Hi all,
> Now with this check pointed merge back to trunks which is about to happen in
> 15-20 minutes after some super clean, build, test, run of studio etc, we can
> release shared 1.0-m1 if y'all like. Here's a release plan that Pierre and I
> discussed:
> (0) confirm a stable build in trunk with merge
> (1) commit merge back to trunk
> (2) assign release manager
> (3) modify pom's for new 1.0-m1 version
> (4) confirm stability
> (5) tag, kick off vote
> (6) if vote passes, release
> (7) merge back trunk changes with 1.0-m2-SNAPSHOT version into m1
> (8) rename m1 branches to m2
> In the meantime right after step #1 we can still continue work on stage II
> in the m1 branch.
Before a shared release we need to release three other artifactes:
- project: with updated plugin versions
- checkstyle-configuration: currently a snapshot is used
- junit-addons: currently a snapshot is used
So let's start with them, then we'll see the progress of the m1 branch.
Kind Regards,
Stefan
Re: [Shared] Release plan for 1.0-m1
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Great! :)
Regards,
Pierre-Arnaud
On 10 févr. 2011, at 08:25, Stefan Seelmann wrote:
> On Mon, Feb 7, 2011 at 6:03 PM, Alex Karasulu <ak...@apache.org> wrote:
>> Hi all,
>> Now with this check pointed merge back to trunks which is about to happen in
>> 15-20 minutes after some super clean, build, test, run of studio etc, we can
>> release shared 1.0-m1 if y'all like. Here's a release plan that Pierre and I
>> discussed:
>> (0) confirm a stable build in trunk with merge
>> (1) commit merge back to trunk
>> (2) assign release manager
>> (3) modify pom's for new 1.0-m1 version
>> (4) confirm stability
>
> I did #3 and #4 yesterday.
>
> The version has been modified to 1.0.0-M1-SNAPSHOT, see parallel thread.
>
> Shared, apacheds, and studio builds went fine. ApacheDS started up
> (using apaches/service/apachds.sh script). Studio started up (using
> studio/application/application-macosx-x86_64), About dialog shows
> shared bundles in version 1.0.0.M1-SNAPSHOT. Hudson builds are also
> stable. I downloaded apacheds-1.5.8-SNAPSHOT.zip and Downloaded
> ApacheDirectoryStudio-macosx-x86_64-2.0.0-SNAPSHOT.zip, both startup.
>
> I'll now continue according to
> https://cwiki.apache.org/confluence/display/DIRxDEV/Releasing+Shared
>
> Kind Regards,
> Stefan
>
>> (5) tag, kick off vote
>> (6) if vote passes, release
>> (7) merge back trunk changes with 1.0-m2-SNAPSHOT version into m1
>> (8) rename m1 branches to m2
Re: [Shared] Release plan for 1.0-m1
Posted by Stefan Seelmann <se...@apache.org>.
On Thu, Feb 10, 2011 at 8:25 AM, Stefan Seelmann <se...@apache.org> wrote:
> On Mon, Feb 7, 2011 at 6:03 PM, Alex Karasulu <ak...@apache.org> wrote:
>> Hi all,
>> Now with this check pointed merge back to trunks which is about to happen in
>> 15-20 minutes after some super clean, build, test, run of studio etc, we can
>> release shared 1.0-m1 if y'all like. Here's a release plan that Pierre and I
>> discussed:
>> (0) confirm a stable build in trunk with merge
>> (1) commit merge back to trunk
>> (2) assign release manager
>> (3) modify pom's for new 1.0-m1 version
>> (4) confirm stability
>
> I did #3 and #4 yesterday.
>
> The version has been modified to 1.0.0-M1-SNAPSHOT, see parallel thread.
>
> Shared, apacheds, and studio builds went fine. ApacheDS started up
> (using apaches/service/apachds.sh script). Studio started up (using
> studio/application/application-macosx-x86_64), About dialog shows
> shared bundles in version 1.0.0.M1-SNAPSHOT. Hudson builds are also
> stable. I downloaded apacheds-1.5.8-SNAPSHOT.zip and Downloaded
> ApacheDirectoryStudio-macosx-x86_64-2.0.0-SNAPSHOT.zip, both startup.
>
> I'll now continue according to
> https://cwiki.apache.org/confluence/display/DIRxDEV/Releasing+Shared
I run the process till step 5.
But I found some issues, so we need to rollback, fix, and run it again:
- In LICENSE we list the Bouncy Castle license, however I don't find a
reference where we use it in shared. So we should remove it from
LICENSE.
- The RAT report lists one file: file-review.txt. I think that file
isn't helpful any more because many files were moved around. Can we
remove it?
- The shared-all jar includes all transitive dependencies (slf4j,
antlr, etc.), but the LICENSE and NOTICE files are not correct, that
needs to be fixed.
Another question:
Which artifacts do we ant to release to http://www.apache.org/dist/directory?
- None?
- Only the source (the new org.apache:apache:8 POM configures the
assembly plugin to generate a source-release zip [4])
- Source and binary
Kind Regards,
Stefan
Re: [Shared] Release plan for 1.0-m1
Posted by Stefan Seelmann <se...@apache.org>.
On Mon, Feb 7, 2011 at 6:03 PM, Alex Karasulu <ak...@apache.org> wrote:
> Hi all,
> Now with this check pointed merge back to trunks which is about to happen in
> 15-20 minutes after some super clean, build, test, run of studio etc, we can
> release shared 1.0-m1 if y'all like. Here's a release plan that Pierre and I
> discussed:
> (0) confirm a stable build in trunk with merge
> (1) commit merge back to trunk
> (2) assign release manager
> (3) modify pom's for new 1.0-m1 version
> (4) confirm stability
I did #3 and #4 yesterday.
The version has been modified to 1.0.0-M1-SNAPSHOT, see parallel thread.
Shared, apacheds, and studio builds went fine. ApacheDS started up
(using apaches/service/apachds.sh script). Studio started up (using
studio/application/application-macosx-x86_64), About dialog shows
shared bundles in version 1.0.0.M1-SNAPSHOT. Hudson builds are also
stable. I downloaded apacheds-1.5.8-SNAPSHOT.zip and Downloaded
ApacheDirectoryStudio-macosx-x86_64-2.0.0-SNAPSHOT.zip, both startup.
I'll now continue according to
https://cwiki.apache.org/confluence/display/DIRxDEV/Releasing+Shared
Kind Regards,
Stefan
> (5) tag, kick off vote
> (6) if vote passes, release
> (7) merge back trunk changes with 1.0-m2-SNAPSHOT version into m1
> (8) rename m1 branches to m2
Re: [Shared] Release plan for 1.0-m1
Posted by Alex Karasulu <ak...@apache.org>.
On Mon, Feb 7, 2011 at 7:47 PM, Stefan Seelmann <se...@apache.org> wrote:
> On Mon, Feb 7, 2011 at 6:03 PM, Alex Karasulu <ak...@apache.org> wrote:
>> Hi all,
>> Now with this check pointed merge back to trunks which is about to happen in
>> 15-20 minutes after some super clean, build, test, run of studio etc, we can
>> release shared 1.0-m1 if y'all like. Here's a release plan that Pierre and I
>> discussed:
>> (0) confirm a stable build in trunk with merge
>> (1) commit merge back to trunk
>> (2) assign release manager
>> (3) modify pom's for new 1.0-m1 version
>> (4) confirm stability
>> (5) tag, kick off vote
>> (6) if vote passes, release
>> (7) merge back trunk changes with 1.0-m2-SNAPSHOT version into m1
>> (8) rename m1 branches to m2
>> In the meantime right after step #1 we can still continue work on stage II
>> in the m1 branch.
>> Thoughts?
>
> I'd volunteer as RM so Alex, Emmanuel and Pierre-Arnaud can continue
> without slowdown.
Thanks Stefan,
Alex
Re: [Shared] Release plan for 1.0-m1
Posted by Stefan Seelmann <se...@apache.org>.
On Mon, Feb 7, 2011 at 6:03 PM, Alex Karasulu <ak...@apache.org> wrote:
> Hi all,
> Now with this check pointed merge back to trunks which is about to happen in
> 15-20 minutes after some super clean, build, test, run of studio etc, we can
> release shared 1.0-m1 if y'all like. Here's a release plan that Pierre and I
> discussed:
> (0) confirm a stable build in trunk with merge
> (1) commit merge back to trunk
> (2) assign release manager
> (3) modify pom's for new 1.0-m1 version
> (4) confirm stability
> (5) tag, kick off vote
> (6) if vote passes, release
> (7) merge back trunk changes with 1.0-m2-SNAPSHOT version into m1
> (8) rename m1 branches to m2
> In the meantime right after step #1 we can still continue work on stage II
> in the m1 branch.
> Thoughts?
I'd volunteer as RM so Alex, Emmanuel and Pierre-Arnaud can continue
without slowdown.
Kind Regards,
Stefan