You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by Matt Sicker <bo...@gmail.com> on 2017/03/09 04:07:40 UTC
Roadmap for log4j-api-scala 11.0
We've established that this will need to be released before we can
officially remove the equivalent modules from the main log4j repository
(and release cycle). Since the artifacts are no longer tied directly to
log4j-api/core, we've also agreed that it makes sense to version it
separately as well. The latest releases are 2.8.1, so the next version
number proposed is 11.0. I dig the Spinal Tap reference, so let's go for it.
I know that the source and binary distributions assemblies need to be
ported over in order to properly create a release candidate. The site is
pretty bare bones, and Ralph has mentioned that he should be able to take
care of integrating it into the main site. Otherwise, I'll be ready to
start a release candidate hopefully by this weekend.
--
Matt Sicker <bo...@gmail.com>
Re: Roadmap for log4j-api-scala 11.0
Posted by Mikael Ståldal <mi...@magine.com>.
I am still a bit lost. Maybe it's better if Matt does it?
On Thu, Mar 9, 2017 at 5:22 PM, Ralph Goers <ra...@dslextreme.com>
wrote:
> The distribution zip and tarball contain all the artifacts that are being
> released - i.e. the jars. The Log4j distribution includes all the jars
> from all the sub projects. Obviously, the Scala distribution will only
> contain the Scala jars. So the assembly xml file needs to be modified to
> only include what is being released. The distribution source and zip are
> what the ASF actually considers to be the release. The source distribution
> should just be an exact copy of the source tree. It needs to have the
> NOTICE.txt, LICENSE.txt and should have a README.md and any other text
> files you want people to be able review when looking at the repo on GitHub.
> You can copy most of these files from the Log4j root directory. The
> NOTICE.txt file should be modified to remove the things that don’t apply to
> the Scala project (I believe that is the last 3 items).
>
> Ralph
>
> On Mar 9, 2017, at 8:59 AM, Mikael Ståldal <mi...@magine.com>
> wrote:
>
> I am a bit lost here.
>
> On Thu, Mar 9, 2017 at 4:56 PM, Mikael Ståldal <mi...@magine.com>
> wrote:
>
>> Change to what?
>>
>> On Thu, Mar 9, 2017 at 4:32 PM, Ralph Goers <ra...@dslextreme.com>
>> wrote:
>>
>>> The instructions for what will be in the zip and tar balls will have to
>>> change.
>>>
>>> Ralph
>>>
>>> On Mar 9, 2017, at 8:01 AM, Matt Sicker <bo...@gmail.com> wrote:
>>>
>>> If you have time before the weekend, you could try copying over the
>>> log4j-distribution section from the main pom files. The "release" maven
>>> profile should activate it I believe, so you should see the generated zips
>>> and tarballs.
>>>
>>> On 9 March 2017 at 03:01, Mikael Ståldal <mi...@magine.com>
>>> wrote:
>>>
>>>> Nice! Tell me if there is anything I can do to help out.
>>>>
>>>> On Thu, Mar 9, 2017 at 5:07 AM, Matt Sicker <bo...@gmail.com> wrote:
>>>>
>>>>> We've established that this will need to be released before we can
>>>>> officially remove the equivalent modules from the main log4j repository
>>>>> (and release cycle). Since the artifacts are no longer tied directly to
>>>>> log4j-api/core, we've also agreed that it makes sense to version it
>>>>> separately as well. The latest releases are 2.8.1, so the next version
>>>>> number proposed is 11.0. I dig the Spinal Tap reference, so let's go for it.
>>>>>
>>>>> I know that the source and binary distributions assemblies need to be
>>>>> ported over in order to properly create a release candidate. The site is
>>>>> pretty bare bones, and Ralph has mentioned that he should be able to take
>>>>> care of integrating it into the main site. Otherwise, I'll be ready to
>>>>> start a release candidate hopefully by this weekend.
>>>>>
>>>>> --
>>>>> Matt Sicker <bo...@gmail.com>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> [image: MagineTV]
>>>>
>>>> *Mikael Ståldal*
>>>> Senior software developer
>>>>
>>>> *Magine TV*
>>>> mikael.staldal@magine.com
>>>> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
>>>> <http://www.magine.com/>
>>>>
>>>> Privileged and/or Confidential Information may be contained in this
>>>> message. If you are not the addressee indicated in this message
>>>> (or responsible for delivery of the message to such a person), you may
>>>> not copy or deliver this message to anyone. In such case,
>>>> you should destroy this message and kindly notify the sender by reply
>>>> email.
>>>>
>>>
>>>
>>>
>>> --
>>> Matt Sicker <bo...@gmail.com>
>>>
>>>
>>>
>>
>>
>> --
>> [image: MagineTV]
>>
>> *Mikael Ståldal*
>> Senior software developer
>>
>> *Magine TV*
>> mikael.staldal@magine.com
>> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
>>
>> Privileged and/or Confidential Information may be contained in this
>> message. If you are not the addressee indicated in this message
>> (or responsible for delivery of the message to such a person), you may
>> not copy or deliver this message to anyone. In such case,
>> you should destroy this message and kindly notify the sender by reply
>> email.
>>
>
>
>
> --
> [image: MagineTV]
>
> *Mikael Ståldal*
> Senior software developer
>
> *Magine TV*
> mikael.staldal@magine.com
> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
>
> Privileged and/or Confidential Information may be contained in this
> message. If you are not the addressee indicated in this message
> (or responsible for delivery of the message to such a person), you may not
> copy or deliver this message to anyone. In such case,
> you should destroy this message and kindly notify the sender by reply
> email.
>
>
>
--
[image: MagineTV]
*Mikael Ståldal*
Senior software developer
*Magine TV*
mikael.staldal@magine.com
Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
Privileged and/or Confidential Information may be contained in this
message. If you are not the addressee indicated in this message
(or responsible for delivery of the message to such a person), you may not
copy or deliver this message to anyone. In such case,
you should destroy this message and kindly notify the sender by reply
email.
Re: Roadmap for log4j-api-scala 11.0
Posted by Ralph Goers <ra...@dslextreme.com>.
The distribution zip and tarball contain all the artifacts that are being released - i.e. the jars. The Log4j distribution includes all the jars from all the sub projects. Obviously, the Scala distribution will only contain the Scala jars. So the assembly xml file needs to be modified to only include what is being released. The distribution source and zip are what the ASF actually considers to be the release. The source distribution should just be an exact copy of the source tree. It needs to have the NOTICE.txt, LICENSE.txt and should have a README.md and any other text files you want people to be able review when looking at the repo on GitHub. You can copy most of these files from the Log4j root directory. The NOTICE.txt file should be modified to remove the things that don’t apply to the Scala project (I believe that is the last 3 items).
Ralph
> On Mar 9, 2017, at 8:59 AM, Mikael Ståldal <mi...@magine.com> wrote:
>
> I am a bit lost here.
>
> On Thu, Mar 9, 2017 at 4:56 PM, Mikael Ståldal <mikael.staldal@magine.com <ma...@magine.com>> wrote:
> Change to what?
>
> On Thu, Mar 9, 2017 at 4:32 PM, Ralph Goers <ralph.goers@dslextreme.com <ma...@dslextreme.com>> wrote:
> The instructions for what will be in the zip and tar balls will have to change.
>
> Ralph
>
>> On Mar 9, 2017, at 8:01 AM, Matt Sicker <boards@gmail.com <ma...@gmail.com>> wrote:
>>
>> If you have time before the weekend, you could try copying over the log4j-distribution section from the main pom files. The "release" maven profile should activate it I believe, so you should see the generated zips and tarballs.
>>
>> On 9 March 2017 at 03:01, Mikael Ståldal <mikael.staldal@magine.com <ma...@magine.com>> wrote:
>> Nice! Tell me if there is anything I can do to help out.
>>
>> On Thu, Mar 9, 2017 at 5:07 AM, Matt Sicker <boards@gmail.com <ma...@gmail.com>> wrote:
>> We've established that this will need to be released before we can officially remove the equivalent modules from the main log4j repository (and release cycle). Since the artifacts are no longer tied directly to log4j-api/core, we've also agreed that it makes sense to version it separately as well. The latest releases are 2.8.1, so the next version number proposed is 11.0. I dig the Spinal Tap reference, so let's go for it.
>>
>> I know that the source and binary distributions assemblies need to be ported over in order to properly create a release candidate. The site is pretty bare bones, and Ralph has mentioned that he should be able to take care of integrating it into the main site. Otherwise, I'll be ready to start a release candidate hopefully by this weekend.
>>
>> --
>> Matt Sicker <boards@gmail.com <ma...@gmail.com>>
>>
>>
>>
>> --
>>
>>
>> Mikael Ståldal
>> Senior software developer
>>
>> Magine TV
>> mikael.staldal@magine.com <ma...@magine.com>
>> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com <http://www.magine.com/>
>>
>> Privileged and/or Confidential Information may be contained in this message. If you are not the addressee indicated in this message
>> (or responsible for delivery of the message to such a person), you may not copy or deliver this message to anyone. In such case,
>> you should destroy this message and kindly notify the sender by reply email.
>>
>>
>>
>> --
>> Matt Sicker <boards@gmail.com <ma...@gmail.com>>
>
>
>
>
> --
>
>
> Mikael Ståldal
> Senior software developer
>
> Magine TV
> mikael.staldal@magine.com <ma...@magine.com>
> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com <http://www.magine.com/>
>
> Privileged and/or Confidential Information may be contained in this message. If you are not the addressee indicated in this message
> (or responsible for delivery of the message to such a person), you may not copy or deliver this message to anyone. In such case,
> you should destroy this message and kindly notify the sender by reply email.
>
>
>
> --
>
>
> Mikael Ståldal
> Senior software developer
>
> Magine TV
> mikael.staldal@magine.com <ma...@magine.com>
> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com <http://www.magine.com/>
>
> Privileged and/or Confidential Information may be contained in this message. If you are not the addressee indicated in this message
> (or responsible for delivery of the message to such a person), you may not copy or deliver this message to anyone. In such case,
> you should destroy this message and kindly notify the sender by reply email.
Re: Roadmap for log4j-api-scala 11.0
Posted by Mikael Ståldal <mi...@magine.com>.
I am a bit lost here.
On Thu, Mar 9, 2017 at 4:56 PM, Mikael Ståldal <mi...@magine.com>
wrote:
> Change to what?
>
> On Thu, Mar 9, 2017 at 4:32 PM, Ralph Goers <ra...@dslextreme.com>
> wrote:
>
>> The instructions for what will be in the zip and tar balls will have to
>> change.
>>
>> Ralph
>>
>> On Mar 9, 2017, at 8:01 AM, Matt Sicker <bo...@gmail.com> wrote:
>>
>> If you have time before the weekend, you could try copying over the
>> log4j-distribution section from the main pom files. The "release" maven
>> profile should activate it I believe, so you should see the generated zips
>> and tarballs.
>>
>> On 9 March 2017 at 03:01, Mikael Ståldal <mi...@magine.com>
>> wrote:
>>
>>> Nice! Tell me if there is anything I can do to help out.
>>>
>>> On Thu, Mar 9, 2017 at 5:07 AM, Matt Sicker <bo...@gmail.com> wrote:
>>>
>>>> We've established that this will need to be released before we can
>>>> officially remove the equivalent modules from the main log4j repository
>>>> (and release cycle). Since the artifacts are no longer tied directly to
>>>> log4j-api/core, we've also agreed that it makes sense to version it
>>>> separately as well. The latest releases are 2.8.1, so the next version
>>>> number proposed is 11.0. I dig the Spinal Tap reference, so let's go for it.
>>>>
>>>> I know that the source and binary distributions assemblies need to be
>>>> ported over in order to properly create a release candidate. The site is
>>>> pretty bare bones, and Ralph has mentioned that he should be able to take
>>>> care of integrating it into the main site. Otherwise, I'll be ready to
>>>> start a release candidate hopefully by this weekend.
>>>>
>>>> --
>>>> Matt Sicker <bo...@gmail.com>
>>>>
>>>
>>>
>>>
>>> --
>>> [image: MagineTV]
>>>
>>> *Mikael Ståldal*
>>> Senior software developer
>>>
>>> *Magine TV*
>>> mikael.staldal@magine.com
>>> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
>>> <http://www.magine.com/>
>>>
>>> Privileged and/or Confidential Information may be contained in this
>>> message. If you are not the addressee indicated in this message
>>> (or responsible for delivery of the message to such a person), you may
>>> not copy or deliver this message to anyone. In such case,
>>> you should destroy this message and kindly notify the sender by reply
>>> email.
>>>
>>
>>
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>>
>>
>>
>
>
> --
> [image: MagineTV]
>
> *Mikael Ståldal*
> Senior software developer
>
> *Magine TV*
> mikael.staldal@magine.com
> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
>
> Privileged and/or Confidential Information may be contained in this
> message. If you are not the addressee indicated in this message
> (or responsible for delivery of the message to such a person), you may not
> copy or deliver this message to anyone. In such case,
> you should destroy this message and kindly notify the sender by reply
> email.
>
--
[image: MagineTV]
*Mikael Ståldal*
Senior software developer
*Magine TV*
mikael.staldal@magine.com
Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
Privileged and/or Confidential Information may be contained in this
message. If you are not the addressee indicated in this message
(or responsible for delivery of the message to such a person), you may not
copy or deliver this message to anyone. In such case,
you should destroy this message and kindly notify the sender by reply
email.
Re: Roadmap for log4j-api-scala 11.0
Posted by Mikael Ståldal <mi...@magine.com>.
Change to what?
On Thu, Mar 9, 2017 at 4:32 PM, Ralph Goers <ra...@dslextreme.com>
wrote:
> The instructions for what will be in the zip and tar balls will have to
> change.
>
> Ralph
>
> On Mar 9, 2017, at 8:01 AM, Matt Sicker <bo...@gmail.com> wrote:
>
> If you have time before the weekend, you could try copying over the
> log4j-distribution section from the main pom files. The "release" maven
> profile should activate it I believe, so you should see the generated zips
> and tarballs.
>
> On 9 March 2017 at 03:01, Mikael Ståldal <mi...@magine.com>
> wrote:
>
>> Nice! Tell me if there is anything I can do to help out.
>>
>> On Thu, Mar 9, 2017 at 5:07 AM, Matt Sicker <bo...@gmail.com> wrote:
>>
>>> We've established that this will need to be released before we can
>>> officially remove the equivalent modules from the main log4j repository
>>> (and release cycle). Since the artifacts are no longer tied directly to
>>> log4j-api/core, we've also agreed that it makes sense to version it
>>> separately as well. The latest releases are 2.8.1, so the next version
>>> number proposed is 11.0. I dig the Spinal Tap reference, so let's go for it.
>>>
>>> I know that the source and binary distributions assemblies need to be
>>> ported over in order to properly create a release candidate. The site is
>>> pretty bare bones, and Ralph has mentioned that he should be able to take
>>> care of integrating it into the main site. Otherwise, I'll be ready to
>>> start a release candidate hopefully by this weekend.
>>>
>>> --
>>> Matt Sicker <bo...@gmail.com>
>>>
>>
>>
>>
>> --
>> [image: MagineTV]
>>
>> *Mikael Ståldal*
>> Senior software developer
>>
>> *Magine TV*
>> mikael.staldal@magine.com
>> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
>> <http://www.magine.com/>
>>
>> Privileged and/or Confidential Information may be contained in this
>> message. If you are not the addressee indicated in this message
>> (or responsible for delivery of the message to such a person), you may
>> not copy or deliver this message to anyone. In such case,
>> you should destroy this message and kindly notify the sender by reply
>> email.
>>
>
>
>
> --
> Matt Sicker <bo...@gmail.com>
>
>
>
--
[image: MagineTV]
*Mikael Ståldal*
Senior software developer
*Magine TV*
mikael.staldal@magine.com
Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
Privileged and/or Confidential Information may be contained in this
message. If you are not the addressee indicated in this message
(or responsible for delivery of the message to such a person), you may not
copy or deliver this message to anyone. In such case,
you should destroy this message and kindly notify the sender by reply
email.
Re: Roadmap for log4j-api-scala 11.0
Posted by Ralph Goers <ra...@dslextreme.com>.
The instructions for what will be in the zip and tar balls will have to change.
Ralph
> On Mar 9, 2017, at 8:01 AM, Matt Sicker <bo...@gmail.com> wrote:
>
> If you have time before the weekend, you could try copying over the log4j-distribution section from the main pom files. The "release" maven profile should activate it I believe, so you should see the generated zips and tarballs.
>
> On 9 March 2017 at 03:01, Mikael Ståldal <mikael.staldal@magine.com <ma...@magine.com>> wrote:
> Nice! Tell me if there is anything I can do to help out.
>
> On Thu, Mar 9, 2017 at 5:07 AM, Matt Sicker <boards@gmail.com <ma...@gmail.com>> wrote:
> We've established that this will need to be released before we can officially remove the equivalent modules from the main log4j repository (and release cycle). Since the artifacts are no longer tied directly to log4j-api/core, we've also agreed that it makes sense to version it separately as well. The latest releases are 2.8.1, so the next version number proposed is 11.0. I dig the Spinal Tap reference, so let's go for it.
>
> I know that the source and binary distributions assemblies need to be ported over in order to properly create a release candidate. The site is pretty bare bones, and Ralph has mentioned that he should be able to take care of integrating it into the main site. Otherwise, I'll be ready to start a release candidate hopefully by this weekend.
>
> --
> Matt Sicker <boards@gmail.com <ma...@gmail.com>>
>
>
>
> --
>
>
> Mikael Ståldal
> Senior software developer
>
> Magine TV
> mikael.staldal@magine.com <ma...@magine.com>
> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com <http://www.magine.com/>
>
> Privileged and/or Confidential Information may be contained in this message. If you are not the addressee indicated in this message
> (or responsible for delivery of the message to such a person), you may not copy or deliver this message to anyone. In such case,
> you should destroy this message and kindly notify the sender by reply email.
>
>
>
> --
> Matt Sicker <boards@gmail.com <ma...@gmail.com>>
Re: Roadmap for log4j-api-scala 11.0
Posted by Matt Sicker <bo...@gmail.com>.
If you have time before the weekend, you could try copying over the
log4j-distribution section from the main pom files. The "release" maven
profile should activate it I believe, so you should see the generated zips
and tarballs.
On 9 March 2017 at 03:01, Mikael Ståldal <mi...@magine.com> wrote:
> Nice! Tell me if there is anything I can do to help out.
>
> On Thu, Mar 9, 2017 at 5:07 AM, Matt Sicker <bo...@gmail.com> wrote:
>
>> We've established that this will need to be released before we can
>> officially remove the equivalent modules from the main log4j repository
>> (and release cycle). Since the artifacts are no longer tied directly to
>> log4j-api/core, we've also agreed that it makes sense to version it
>> separately as well. The latest releases are 2.8.1, so the next version
>> number proposed is 11.0. I dig the Spinal Tap reference, so let's go for it.
>>
>> I know that the source and binary distributions assemblies need to be
>> ported over in order to properly create a release candidate. The site is
>> pretty bare bones, and Ralph has mentioned that he should be able to take
>> care of integrating it into the main site. Otherwise, I'll be ready to
>> start a release candidate hopefully by this weekend.
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>>
>
>
>
> --
> [image: MagineTV]
>
> *Mikael Ståldal*
> Senior software developer
>
> *Magine TV*
> mikael.staldal@magine.com
> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
>
> Privileged and/or Confidential Information may be contained in this
> message. If you are not the addressee indicated in this message
> (or responsible for delivery of the message to such a person), you may not
> copy or deliver this message to anyone. In such case,
> you should destroy this message and kindly notify the sender by reply
> email.
>
--
Matt Sicker <bo...@gmail.com>
Re: Roadmap for log4j-api-scala 11.0
Posted by Mikael Ståldal <mi...@magine.com>.
Nice! Tell me if there is anything I can do to help out.
On Thu, Mar 9, 2017 at 5:07 AM, Matt Sicker <bo...@gmail.com> wrote:
> We've established that this will need to be released before we can
> officially remove the equivalent modules from the main log4j repository
> (and release cycle). Since the artifacts are no longer tied directly to
> log4j-api/core, we've also agreed that it makes sense to version it
> separately as well. The latest releases are 2.8.1, so the next version
> number proposed is 11.0. I dig the Spinal Tap reference, so let's go for it.
>
> I know that the source and binary distributions assemblies need to be
> ported over in order to properly create a release candidate. The site is
> pretty bare bones, and Ralph has mentioned that he should be able to take
> care of integrating it into the main site. Otherwise, I'll be ready to
> start a release candidate hopefully by this weekend.
>
> --
> Matt Sicker <bo...@gmail.com>
>
--
[image: MagineTV]
*Mikael Ståldal*
Senior software developer
*Magine TV*
mikael.staldal@magine.com
Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
Privileged and/or Confidential Information may be contained in this
message. If you are not the addressee indicated in this message
(or responsible for delivery of the message to such a person), you may not
copy or deliver this message to anyone. In such case,
you should destroy this message and kindly notify the sender by reply
email.