Yea I figured we should wait on the new master pom. Once that is completed
I'll restart the release process.

I had some local dev environment issues with the maven release plugin but I
think I have those resolved now. Should be pretty simple to get the release
completed now.

Are there any additional steps we need to take in myfaces core to pick up
the new master pom?


Thanks,

Paul Nicolucci



From:   Thomas Andraschko <andraschko.tho...@gmail.com>
To:     MyFaces Development <dev@myfaces.apache.org>
Date:   08/27/2018 06:30 AM
Subject:        Re: 2.3.2 Release



Any news Paul?
We should wait for the new master pom and then release it asap
Afaik TomEE would also like to release soon and 2.3.2 contains important
bugfixes

Paul Nicolucci <pnico...@us.ibm.com> schrieb am Di., 21. Aug. 2018, 22:01:
  I got busy with some day to day work. I'll get back to this now.

  Thanks,

  Paul Nicolucci


  "Paul Nicolucci" ---08/06/2018 08:54:59 PM---I'll start on a release
  later this week for MyFaces 2.3.2. Stay tuned for updates as I make
  progress

  From: "Paul Nicolucci" <pnico...@us.ibm.com>
  To: "MyFaces Development" <dev@myfaces.apache.org>
  Date: 08/06/2018 08:54 PM
  Subject: Re: 2.3.2 Release



  I'll start on a release later this week for MyFaces 2.3.2.

  Stay tuned for updates as I make progress.

  Thanks,

  Paul

  Thomas Andraschko ---08/06/2018 05:47:55 PM---What about a release soon?
  Paul?! 2018-07-07 13:19 GMT+02:00 Dennis Kieselhorst <d...@apache.org>:

  From: Thomas Andraschko <andraschko.tho...@gmail.com>
  To: MyFaces Development <dev@myfaces.apache.org>
  Date: 08/06/2018 05:47 PM
  Subject: Re: 2.3.2 Release



  What about a release soon? Paul?!

  2018-07-07 13:19 GMT+02:00 Dennis Kieselhorst <d...@apache.org>:
              Hi!

              > In the meantime, I have some questions after the move to
              Git. I'm not sure
              > if after the move, we have to modify some pom.xml files, do
              you guys know
              > if we have to make any modification? Does the release
              process stay the
              > same? Any help here would be great.

              I've changed the scm section from svn to git directly after
              the migration but you're right there may be other places
              where we have to modify something. My suggestion is to cut a
              release and let the list know if there are some problems. We
              have some experiences from the Tobago migration, afaik there
              were no big problems.

              Please note that the site/ publishing stuff is still in SVN,
              so no changes required in this area.

              Regards
              Dennis




  [attachment "graycol.gif" deleted by Paul Nicolucci/Durham/IBM]





Reply via email to