Re: [DISCUSS] Next releases

[Francesco Chicchiriccò]

Hi all,
update on this topic: all the three items below are now done.

I have opened SYNCOPE-1332 to track the work around Java 9/10 on the 
master branch.


IMO, we should focus now in defining what to put in 3.0.0.

Regards.

On 12/06/2018 16:46, Francesco Chicchiriccò wrote:

Hi all,
as you might have noticed, 2.0.9 is already full of fixes and new 
features as the OpenID Connect Client extension and the Docker images 
[1].
To me, the only blocker for proceeding with such release is the 
availability of CXF 3.1.16, which should take place soon according to 
the existing discussion there.


Moreover, with recent release of OpenJPA 3.0.0, one of the biggest 
blockers for 2.1.0 was removed; currently, the only one is CXF 3.2.5, 
which should follow the same timeline as above.
There are other pending issues to do [2], which could be moved to 
2.1.1 or even to next stable 3.0.0.


I propose to:

1. proceed with 2.0.9 and 2.1.0 as soon as CXF releases are available
2. as consequence of 2.1.0, a new 2_1_X branch will be created, and 
master will get 3.0.0-SNAPSHOT
3. since 2_0_X has java 7 compatibility, 2_1_X will retain java 8, and 
master java 9+


WDYT?
Regards.

[1] https://issues.apache.org/jira/projects/SYNCOPE/versions/12342943
[2] https://issues.apache.org/jira/projects/SYNCOPE/versions/12334366


--
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
http://home.apache.org/~ilgrosso/

Re: [DISCUSS] Next releases

[Marco Di Sabatino Di Diodoro]

Il 12/06/2018 16:46, Francesco Chicchiriccò ha scritto:

Hi all,
as you might have noticed, 2.0.9 is already full of fixes and new 
features as the OpenID Connect Client extension and the Docker images 
[1].
To me, the only blocker for proceeding with such release is the 
availability of CXF 3.1.16, which should take place soon according to 
the existing discussion there.


Moreover, with recent release of OpenJPA 3.0.0, one of the biggest 
blockers for 2.1.0 was removed; currently, the only one is CXF 3.2.5, 
which should follow the same timeline as above.
There are other pending issues to do [2], which could be moved to 
2.1.1 or even to next stable 3.0.0.


I propose to:

1. proceed with 2.0.9 and 2.1.0 as soon as CXF releases are available
2. as consequence of 2.1.0, a new 2_1_X branch will be created, and 
master will get 3.0.0-SNAPSHOT
3. since 2_0_X has java 7 compatibility, 2_1_X will retain java 8, and 
master java 9+


WDYT?
Regards.


+1
M


[1] https://issues.apache.org/jira/projects/SYNCOPE/versions/12342943
[2] https://issues.apache.org/jira/projects/SYNCOPE/versions/12334366



--
Dott. Marco Di Sabatino Di Diodoro
Tel. +39 3939065570

Tirasa S.r.l.
Viale Vittoria Colonna, 97 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

Apache Syncope PMC Member
http://people.apache.org/~mdisabatino/

Re: [DISCUSS] Next releases

[Matteo Alessandroni]

Hi,

sounds great to me!
+1

Best regards,
Matteo

On 12/06/2018 16:46, Francesco Chicchiriccò wrote:

Hi all,
as you might have noticed, 2.0.9 is already full of fixes and new 
features as the OpenID Connect Client extension and the Docker images 
[1].
To me, the only blocker for proceeding with such release is the 
availability of CXF 3.1.16, which should take place soon according to 
the existing discussion there.


Moreover, with recent release of OpenJPA 3.0.0, one of the biggest 
blockers for 2.1.0 was removed; currently, the only one is CXF 3.2.5, 
which should follow the same timeline as above.
There are other pending issues to do [2], which could be moved to 
2.1.1 or even to next stable 3.0.0.


I propose to:

1. proceed with 2.0.9 and 2.1.0 as soon as CXF releases are available
2. as consequence of 2.1.0, a new 2_1_X branch will be created, and 
master will get 3.0.0-SNAPSHOT
3. since 2_0_X has java 7 compatibility, 2_1_X will retain java 8, and 
master java 9+


WDYT?
Regards.

[1] https://issues.apache.org/jira/projects/SYNCOPE/versions/12342943
[2] https://issues.apache.org/jira/projects/SYNCOPE/versions/12334366



--

Dott. Matteo Alessandroni

Software Engineer @ Tirasa S.r.l.

Viale Vittoria Colonna, 97 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973

http://www.tirasa.net

Apache Syncope PMC Member
http://people.apache.org/phonebook.html?uid=skylark17 



Tirasa S.r.l. 

Re: [DISCUSS] Next releases

[Matteo Di Carlo]

+1, sounds good to me.

Matteo


On 12/06/2018 16:46, Francesco Chicchiriccò wrote:

Hi all,
as you might have noticed, 2.0.9 is already full of fixes and new 
features as the OpenID Connect Client extension and the Docker images 
[1].
To me, the only blocker for proceeding with such release is the 
availability of CXF 3.1.16, which should take place soon according to 
the existing discussion there.


Moreover, with recent release of OpenJPA 3.0.0, one of the biggest 
blockers for 2.1.0 was removed; currently, the only one is CXF 3.2.5, 
which should follow the same timeline as above.
There are other pending issues to do [2], which could be moved to 
2.1.1 or even to next stable 3.0.0.


I propose to:

1. proceed with 2.0.9 and 2.1.0 as soon as CXF releases are available
2. as consequence of 2.1.0, a new 2_1_X branch will be created, and 
master will get 3.0.0-SNAPSHOT
3. since 2_0_X has java 7 compatibility, 2_1_X will retain java 8, and 
master java 9+


WDYT?
Regards.

[1] https://issues.apache.org/jira/projects/SYNCOPE/versions/12342943
[2] https://issues.apache.org/jira/projects/SYNCOPE/versions/12334366

Re: [DISCUSS] Next releases

[Andrea Patricelli]

Il 12/06/2018 16:46, Francesco Chicchiriccò ha scritto:

Hi all,
as you might have noticed, 2.0.9 is already full of fixes and new 
features as the OpenID Connect Client extension and the Docker images 
[1].
To me, the only blocker for proceeding with such release is the 
availability of CXF 3.1.16, which should take place soon according to 
the existing discussion there.


Moreover, with recent release of OpenJPA 3.0.0, one of the biggest 
blockers for 2.1.0 was removed; currently, the only one is CXF 3.2.5, 
which should follow the same timeline as above.
There are other pending issues to do [2], which could be moved to 
2.1.1 or even to next stable 3.0.0.


I propose to:

1. proceed with 2.0.9 and 2.1.0 as soon as CXF releases are available
2. as consequence of 2.1.0, a new 2_1_X branch will be created, and 
master will get 3.0.0-SNAPSHOT
3. since 2_0_X has java 7 compatibility, 2_1_X will retain java 8, and 
master java 9+


WDYT?


+1


Regards.

[1] https://issues.apache.org/jira/projects/SYNCOPE/versions/12342943
[2] https://issues.apache.org/jira/projects/SYNCOPE/versions/12334366


Best regards,
Andrea

--
Dott. Andrea Patricelli
Tel. +39 3204524292

Developer @ Tirasa S.r.l.
Viale D'Annunzio 267 - 65127 Pescara
Tel +39 0859116307 / FAX +39 085973
http://www.tirasa.net

Apache Syncope PMC Member

Re: [DISCUSS] Next releases

[Francesco Chicchiriccò]

Hi all,
as proposed below, I went ahead and created the 2_0_X maintenance branch 
from master, then set version 2.1.0-SNAPSHOT and JDK 1.8 for master.


Regards.

On 05/09/2016 17:21, Colm O hEigeartaigh wrote:

+1.

Colm.

On Mon, Sep 5, 2016 at 4:16 PM, Francesco Chicchiriccò 
wrote:


Hi all,
as 2.0.0.M5 is done, we'll continue as scheduled with 2.0.0, possibly this
Friday.

After that, I would like to

1. create 2_0_X for maintenance from master
2. set version to 2.1.0-SNAPHOST + Java compatibility to 1.8 on master

WDYT?

On 2016-08-24 09:54 (+0200), Francesco Chicchiriccò 
wrote:

Hi all,
the work towards 2.0.0 seems to be almost complete: I should be able to
finish the larger missing part (e.g. documentation as per SYNCOPE-700)
by the end of this week.

At that point I would like to cut the last milestone release 2.0.0-M5
(mainly to verify once more that the release process is tuned up) then,
after a week or two, go out with 2.0.0.

Do you see any problems with this approach?
Regards.


--
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC,
CXF Committer, OpenJPA Committer, PonyMail PPMC
http://home.apache.org/~ilgrosso/

Re: [DISCUSS] Next releases

[Colm O hEigeartaigh]

+1.

Colm.

On Mon, Sep 5, 2016 at 4:16 PM, Francesco Chicchiriccò 
wrote:

> Hi all,
> as 2.0.0.M5 is done, we'll continue as scheduled with 2.0.0, possibly this
> Friday.
>
> After that, I would like to
>
> 1. create 2_0_X for maintenance from master
> 2. set version to 2.1.0-SNAPHOST + Java compatibility to 1.8 on master
>
> WDYT?
>
> On 2016-08-24 09:54 (+0200), Francesco Chicchiriccò 
> wrote:
> > Hi all,
> > the work towards 2.0.0 seems to be almost complete: I should be able to
> > finish the larger missing part (e.g. documentation as per SYNCOPE-700)
> > by the end of this week.
> >
> > At that point I would like to cut the last milestone release 2.0.0-M5
> > (mainly to verify once more that the release process is tuned up) then,
> > after a week or two, go out with 2.0.0.
> >
> > Do you see any problems with this approach?
> > Regards.
>



-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

Re: [DISCUSS] Next releases

[Francesco Chicchiriccò]

Hi all,
as 2.0.0.M5 is done, we'll continue as scheduled with 2.0.0, possibly this 
Friday.

After that, I would like to

1. create 2_0_X for maintenance from master
2. set version to 2.1.0-SNAPHOST + Java compatibility to 1.8 on master

WDYT?

On 2016-08-24 09:54 (+0200), Francesco Chicchiriccò  
wrote: 
> Hi all,
> the work towards 2.0.0 seems to be almost complete: I should be able to 
> finish the larger missing part (e.g. documentation as per SYNCOPE-700) 
> by the end of this week.
> 
> At that point I would like to cut the last milestone release 2.0.0-M5 
> (mainly to verify once more that the release process is tuned up) then, 
> after a week or two, go out with 2.0.0.
> 
> Do you see any problems with this approach?
> Regards.

Re: [DISCUSS] Next releases

[Tushar Mishra]

It does indeed. Thanks!

On Sat, Sep 3, 2016 at 5:54 PM Francesco Chicchiriccò 
wrote:

> On 01/09/2016 18:21, Tushar Mishra wrote:
> > Hi,
> >
> > I wish to help solve the problem with the eclipse plugin. Can I know the
> > details about it? Is there a JIRA issue or a build log that I can consult
> > to start working on it? Or maybe you could explain the problem, so I can
> > figure out the details myself.
>
> As you might imagine since the vote for 2.0.0.M5 is currently in
> progress, I've finally managed to solve the issues mentioned above.
>
> Essentially, I had two problems:
>
> 1. The maven release plugin - used by our release process [1] - does not
> manage version numbers in MANIFEST.MF, only pom.xml, so during the
> release:prepare phase, Tycho was complaining about version mismatch, as
> Bundle-Version [2] is statically set to 2.0.0.qualifier - which works
> well only when pom version ends with -SNAPSHOT.
>
> After spending some time in finding a proper fix, I ended up by manually
> updating the version number [2] to 2.0.0.M5 (as 2.0.0-M5 was not
> accepted) right before running release:prepare and restoring it to
> 2.0.0.qualifier right before release:perform.
> I will update [1] with such steps for future releases.
>
> 2. The apache-release profile defined in the ASF parent pom [3] ensures,
> among other things, to generate the '*-source-release.zip' assembly
> containing the project sources during the release process.
> Unfortunately, such assembly is not smart enough to exclude the content
> of the (non-standard)
>
> ide/eclipse/bundles/org.apache.syncope.ide.eclipse.plugin/lib/
>
> and
>
> ide/eclipse/bundles/org.apache.syncope.ide.eclipse.plugin/bin/
>
> directories, populated by binary artifacts during the build process.
> For this reason I had to override the source assembly with our new local
> one [4].
>
> Hope this clarifies.
> Regards.
>
> [1] http://syncope.apache.org/release-process.html#Prepare_the_release
> [2]
>
> https://github.com/apache/syncope/blob/master/ide/eclipse/bundles/org.apache.syncope.ide.eclipse.plugin/META-INF/MANIFEST.MF#L5
> [3] http://repo1.maven.org/maven2/org/apache/apache/18/apache-18.pom
> [4]
>
> https://github.com/apache/syncope/blob/master/src/assemble/source-release.xml
>
> > On Thu, Sep 1, 2016 at 9:28 PM Francesco Chicchiriccò <
> ilgro...@apache.org> wrote:
> >
> >> Hi all,
> >> I have solved - well, actually work-arounded - the problem as reported
> >> below, which is also the reason why next release will be 2.0.0.M5, not
> >> 2.0.0-M5 as originally planned. Updates to the release process will
> follow.
> >>
> >> Unfortunately, I have found another issue in the source artifact
> >> generation (again due to the Eclipse IDE plugin), which I should have
> >> solved with
> >>
> >>
> >>
> https://github.com/apache/syncope/commit/57cf286b5c792f80b78415b9fa440f8d7f8fcfc0
> >>
> >> I hope I'll have enough time tomorrow to try again.
> >>
> >> Regards.
> >>
> >> On 27/08/2016 16:57, Francesco Chicchiriccò wrote:
> >>> FYI, I was trying to start the release process for 2.0.0-M5 as said
> >>> below, but encountered some issues during the release:prepare phase,
> >>> with Tycho (comprehensible being this the first release including the
> >>> Eclipse plugin...)
> >>>
> >>> For the moment I have reverted all the changes I made: will try again
> >>> next Thursday.
> >>>
> >>> Regards.
> >>>
> >>> On 2016-08-25 09:32 Francesco Chicchiriccò wrote:
>  On 24/08/2016 16:10, Colm O hEigeartaigh wrote:
> > Sounds good to me, I'll restart looking at the documentation.
>  Thanks Colm: this activity is *extremely* appreciated :-)
>  Regards.
> 
> > On Wed, Aug 24, 2016 at 9:03 AM, Massimiliano Perrone
> >  wrote:
> >> + 1
> >>
> >> Also because this is a very important release so I think it's
> >> better to
> >> wait for half September when will start "the new year" and the
> >> people have
> >> surely finished their holidays.
> >> Regards,
> >> Massi
> >> --
> >> Massimiliano Perrone
> >> Tel +39 393 9121310
> >> Tirasa S.r.l.
> >> http://www.tirasa.net
> >> "L'apprendere molte cose non insegna l'intelligenza"
> >> (Eraclito)
> >>
> >> mercoledì, 24 agosto 2016, 09:54AM +02:00 da Francesco
> >> Chicchiriccò:
> >>
> >>> Hi all,
> >>> the work towards 2.0.0 seems to be almost complete: I should be
> >>> able to
> >>> finish the larger missing part (e.g. documentation as per
> >>> SYNCOPE-700)
> >>> by the end of this week.
> >>>
> >>> At that point I would like to cut the last milestone release
> 2.0.0-M5
> >>> (mainly to verify once more that the release process is tuned up)
> >>> then,
> >>> after a week or two, go out with 2.0.0.
> >>>
> >>> Do you see any problems with this approach?
> >>> Regards.
>
> --
> Francesco Chicchiriccò
>
> 

Re: [DISCUSS] Next releases

[Francesco Chicchiriccò]

On 01/09/2016 18:21, Tushar Mishra wrote:

Hi,

I wish to help solve the problem with the eclipse plugin. Can I know the
details about it? Is there a JIRA issue or a build log that I can consult
to start working on it? Or maybe you could explain the problem, so I can
figure out the details myself.


As you might imagine since the vote for 2.0.0.M5 is currently in 
progress, I've finally managed to solve the issues mentioned above.


Essentially, I had two problems:

1. The maven release plugin - used by our release process [1] - does not 
manage version numbers in MANIFEST.MF, only pom.xml, so during the 
release:prepare phase, Tycho was complaining about version mismatch, as 
Bundle-Version [2] is statically set to 2.0.0.qualifier - which works 
well only when pom version ends with -SNAPSHOT.


After spending some time in finding a proper fix, I ended up by manually 
updating the version number [2] to 2.0.0.M5 (as 2.0.0-M5 was not 
accepted) right before running release:prepare and restoring it to 
2.0.0.qualifier right before release:perform.

I will update [1] with such steps for future releases.

2. The apache-release profile defined in the ASF parent pom [3] ensures, 
among other things, to generate the '*-source-release.zip' assembly 
containing the project sources during the release process. 
Unfortunately, such assembly is not smart enough to exclude the content 
of the (non-standard)


ide/eclipse/bundles/org.apache.syncope.ide.eclipse.plugin/lib/

and

ide/eclipse/bundles/org.apache.syncope.ide.eclipse.plugin/bin/

directories, populated by binary artifacts during the build process.
For this reason I had to override the source assembly with our new local 
one [4].


Hope this clarifies.
Regards.

[1] http://syncope.apache.org/release-process.html#Prepare_the_release
[2] 
https://github.com/apache/syncope/blob/master/ide/eclipse/bundles/org.apache.syncope.ide.eclipse.plugin/META-INF/MANIFEST.MF#L5

[3] http://repo1.maven.org/maven2/org/apache/apache/18/apache-18.pom
[4] 
https://github.com/apache/syncope/blob/master/src/assemble/source-release.xml



On Thu, Sep 1, 2016 at 9:28 PM Francesco Chicchiriccò  
wrote:


Hi all,
I have solved - well, actually work-arounded - the problem as reported
below, which is also the reason why next release will be 2.0.0.M5, not
2.0.0-M5 as originally planned. Updates to the release process will follow.

Unfortunately, I have found another issue in the source artifact
generation (again due to the Eclipse IDE plugin), which I should have
solved with


https://github.com/apache/syncope/commit/57cf286b5c792f80b78415b9fa440f8d7f8fcfc0

I hope I'll have enough time tomorrow to try again.

Regards.

On 27/08/2016 16:57, Francesco Chicchiriccò wrote:

FYI, I was trying to start the release process for 2.0.0-M5 as said
below, but encountered some issues during the release:prepare phase,
with Tycho (comprehensible being this the first release including the
Eclipse plugin...)

For the moment I have reverted all the changes I made: will try again
next Thursday.

Regards.

On 2016-08-25 09:32 Francesco Chicchiriccò wrote:

On 24/08/2016 16:10, Colm O hEigeartaigh wrote:

Sounds good to me, I'll restart looking at the documentation.

Thanks Colm: this activity is *extremely* appreciated :-)
Regards.


On Wed, Aug 24, 2016 at 9:03 AM, Massimiliano Perrone
 wrote:

+ 1

Also because this is a very important release so I think it's
better to
wait for half September when will start "the new year" and the
people have
surely finished their holidays.
Regards,
Massi
--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)

mercoledì, 24 agosto 2016, 09:54AM +02:00 da Francesco
Chicchiriccò:


Hi all,
the work towards 2.0.0 seems to be almost complete: I should be
able to
finish the larger missing part (e.g. documentation as per
SYNCOPE-700)
by the end of this week.

At that point I would like to cut the last milestone release 2.0.0-M5
(mainly to verify once more that the release process is tuned up)
then,
after a week or two, go out with 2.0.0.

Do you see any problems with this approach?
Regards.


--
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC,
CXF Committer, OpenJPA Committer, PonyMail PPMC
http://home.apache.org/~ilgrosso/

Re: [DISCUSS] Next releases

[Francesco Chicchiriccò]

Hi all,
I have solved - well, actually work-arounded - the problem as reported 
below, which is also the reason why next release will be 2.0.0.M5, not 
2.0.0-M5 as originally planned. Updates to the release process will follow.


Unfortunately, I have found another issue in the source artifact 
generation (again due to the Eclipse IDE plugin), which I should have 
solved with


https://github.com/apache/syncope/commit/57cf286b5c792f80b78415b9fa440f8d7f8fcfc0

I hope I'll have enough time tomorrow to try again.

Regards.

On 27/08/2016 16:57, Francesco Chicchiriccò wrote:
FYI, I was trying to start the release process for 2.0.0-M5 as said 
below, but encountered some issues during the release:prepare phase, 
with Tycho (comprehensible being this the first release including the 
Eclipse plugin...)


For the moment I have reverted all the changes I made: will try again 
next Thursday.


Regards.

On 2016-08-25 09:32 Francesco Chicchiriccò wrote:

On 24/08/2016 16:10, Colm O hEigeartaigh wrote:

Sounds good to me, I'll restart looking at the documentation.


Thanks Colm: this activity is *extremely* appreciated :-)
Regards.

On Wed, Aug 24, 2016 at 9:03 AM, Massimiliano Perrone 
 wrote:

+ 1

Also because this is a very important release so I think it's 
better to
wait for half September when will start "the new year" and the 
people have

surely finished their holidays.
Regards,
Massi
--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)

mercoledì, 24 agosto 2016, 09:54AM +02:00 da Francesco 
Chicchiriccò:



Hi all,
the work towards 2.0.0 seems to be almost complete: I should be 
able to
finish the larger missing part (e.g. documentation as per 
SYNCOPE-700)

by the end of this week.

At that point I would like to cut the last milestone release 2.0.0-M5
(mainly to verify once more that the release process is tuned up) 
then,

after a week or two, go out with 2.0.0.

Do you see any problems with this approach?
Regards.




--
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC,
CXF Committer, OpenJPA Committer, PonyMail PPMC
http://home.apache.org/~ilgrosso/

Re: [DISCUSS] Next releases

[Francesco Chicchiriccò]

FYI, I was trying to start the release process for 2.0.0-M5 as said 
below, but encountered some issues during the release:prepare phase, 
with Tycho (comprehensible being this the first release including the 
Eclipse plugin...)


For the moment I have reverted all the changes I made: will try again 
next Thursday.


Regards.

On 2016-08-25 09:32 Francesco Chicchiriccò wrote:

On 24/08/2016 16:10, Colm O hEigeartaigh wrote:

Sounds good to me, I'll restart looking at the documentation.


Thanks Colm: this activity is *extremely* appreciated :-)
Regards.

On Wed, Aug 24, 2016 at 9:03 AM, Massimiliano Perrone 
 wrote:

+ 1

Also because this is a very important release so I think it's better 
to
wait for half September when will start "the new year" and the people 
have

surely finished their holidays.
Regards,
Massi
--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)

mercoledì, 24 agosto 2016, 09:54AM +02:00 da Francesco 
Chicchiriccò:



Hi all,
the work towards 2.0.0 seems to be almost complete: I should be able 
to
finish the larger missing part (e.g. documentation as per 
SYNCOPE-700)

by the end of this week.

At that point I would like to cut the last milestone release 
2.0.0-M5
(mainly to verify once more that the release process is tuned up) 
then,

after a week or two, go out with 2.0.0.

Do you see any problems with this approach?
Regards.

--
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC,
CXF Committer, OpenJPA Committer, PonyMail PPMC
http://home.apache.org/~ilgrosso/

Re: [DISCUSS] Next releases

[Francesco Chicchiriccò]

On 24/08/2016 16:10, Colm O hEigeartaigh wrote:

Sounds good to me, I'll restart looking at the documentation.


Thanks Colm: this activity is *extremely* appreciated :-)
Regards.


On Wed, Aug 24, 2016 at 9:03 AM, Massimiliano Perrone 
 wrote:

+ 1

Also because this is a very important release so I think it's better to
wait for half September when will start "the new year" and the people have
surely finished their holidays.
Regards,
Massi
--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito)

mercoledì, 24 agosto 2016, 09:54AM +02:00 da Francesco 
Chicchiriccò:


Hi all,
the work towards 2.0.0 seems to be almost complete: I should be able to
finish the larger missing part (e.g. documentation as per SYNCOPE-700)
by the end of this week.

At that point I would like to cut the last milestone release 2.0.0-M5
(mainly to verify once more that the release process is tuned up) then,
after a week or two, go out with 2.0.0.

Do you see any problems with this approach?
Regards.


--
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC,
CXF Committer, OpenJPA Committer, PonyMail PPMC
http://home.apache.org/~ilgrosso/

Re: [DISCUSS] Next releases

[Colm O hEigeartaigh]

Sounds good to me, I'll restart looking at the documentation.

Colm.

On Wed, Aug 24, 2016 at 9:03 AM, Massimiliano Perrone <
massimiliano.perr...@tirasa.net> wrote:

>
> + 1
> Also because this is a very important release so I think it's better to
> wait for half September when will start "the new year" and the people have
> surely finished their holidays.
> Regards,
> Massi
> --
> Massimiliano Perrone
> Tel +39 393 9121310
> Tirasa S.r.l.
> http://www.tirasa.net
> "L'apprendere molte cose non insegna l'intelligenza"
> (Eraclito) mercoledì, 24 agosto 2016, 09:54AM +02:00 da Francesco
> Chicchiriccò  ilgro...@apache.org :
>
> >Hi all,
> >the work towards 2.0.0 seems to be almost complete: I should be able to
> >finish the larger missing part (e.g. documentation as per SYNCOPE-700)
> >by the end of this week.
> >
> >At that point I would like to cut the last milestone release 2.0.0-M5
> >(mainly to verify once more that the release process is tuned up) then,
> >after a week or two, go out with 2.0.0.
> >
> >Do you see any problems with this approach?
> >Regards.
> >
> >--
> >Francesco Chicchiriccò
> >
> >Tirasa - Open Source Excellence
> >http://www.tirasa.net/
> >
> >Involved at The Apache Software Foundation:
> >member, Syncope PMC chair, Cocoon PMC, Olingo PMC,
> >CXF Committer, OpenJPA Committer, PonyMail PPMC
> >http://home.apache.org/~ilgrosso/
> >
>



-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

Re: [DISCUSS] Next releases

[Massimiliano Perrone]

+ 1
Also because this is a very important release so I think it's better to wait 
for half September when will start "the new year" and the people have surely 
finished their holidays.
Regards,
Massi
--
Massimiliano Perrone
Tel +39 393 9121310
Tirasa S.r.l.
http://www.tirasa.net
"L'apprendere molte cose non insegna l'intelligenza"
(Eraclito) mercoledì, 24 agosto 2016, 09:54AM +02:00 da Francesco Chicchiriccò  
ilgro...@apache.org :

>Hi all,
>the work towards 2.0.0 seems to be almost complete: I should be able to 
>finish the larger missing part (e.g. documentation as per SYNCOPE-700) 
>by the end of this week.
>
>At that point I would like to cut the last milestone release 2.0.0-M5 
>(mainly to verify once more that the release process is tuned up) then, 
>after a week or two, go out with 2.0.0.
>
>Do you see any problems with this approach?
>Regards.
>
>-- 
>Francesco Chicchiriccò
>
>Tirasa - Open Source Excellence
>http://www.tirasa.net/
>
>Involved at The Apache Software Foundation:
>member, Syncope PMC chair, Cocoon PMC, Olingo PMC,
>CXF Committer, OpenJPA Committer, PonyMail PPMC
>http://home.apache.org/~ilgrosso/
>