From sgilda at redhat.com  Fri Jan  2 10:27:16 2015
From: sgilda at redhat.com (Sande Gilda)
Date: Fri, 02 Jan 2015 10:27:16 -0500
Subject: [jbossdeveloper] New year gift! QSTools 1.5.0.Final released
In-Reply-To: <54A16294.5040500@redhat.com>
References: <54A16294.5040500@redhat.com>
Message-ID: <54A6B8D4.5050007@redhat.com>

Thanks Rafael!

On 12/29/2014 09:17 AM, Rafael Benevides wrote:
> We will begin 2015 with QSTools 1.5.0.Final.
>
> Since 1.4.1.Final release we started a long running path to 1.5.0 and 
> here are the changes/new features:
>
>
> - Updated all references from JDF to "JBoss Developer Materials"
> - Allow ArtifactIdNameChecker to be ignored
> - Make MavenCentralRepositoryChecker to be ignored as default
> - JDF-690 - Changed artifactId from maven-qstools-plugin to qstools 
> <https://issues.jboss.org/browse/JDF-690>
> - JDF-762 - Implemented a new goal: qstools:repositories that allows 
> <repository /> maintenance in pom.xml files 
> <https://issues.jboss.org/browse/JDF-762>
> - JDF-786 - QSTools shows detailed information about its version in 
> report <https://issues.jboss.org/browse/JDF-786>
> - JDF-788 - Check Readme metadata value lenght 
> <https://issues.jboss.org/browse/JDF-788>
>
> More details about setup "approved repositories" can see at 
> http://jboss-developer.github.io/maven-qstools-plugin/#setup-jboss-maven-approved-repositories
>
> Happy new year!
>
> -
> -- 
>
> *Rafael Benevides | Senior Software Engineer*
> JBoss Developer
> M: +55-61-9269-6576
>
> Red Hat
>
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at www.redhat.com <http://www.redhat.com/>
>
> LinkedIn <http://www.linkedin.com/company/3258288> Youtube 
> <https://www.youtube.com/redhatlatam>
>
>
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150102/7a2ec595/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 4815 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150102/7a2ec595/attachment.jpe 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 597 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150102/7a2ec595/attachment.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 616 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150102/7a2ec595/attachment-0001.png 

From sgilda at redhat.com  Fri Jan  2 10:28:42 2015
From: sgilda at redhat.com (Sande Gilda)
Date: Fri, 02 Jan 2015 10:28:42 -0500
Subject: [jbossdeveloper] Update JBoss Developer Materials to Java EE 7
 - JAX-RS Client API
In-Reply-To: <54A195B6.3020504@redhat.com>
References: <53FB2B23.6090802@redhat.com>	<540DF5BC.3020103@redhat.com>	<CAGBoHQU93pCyWnJVrXE+FS9xT166JSbQUag2YANRcJfByBRqJg@mail.gmail.com>	<540EF853.9080405@redhat.com>	<CAGBoHQVoM6vgDnppe3MGCywtQN6Uxjg8zFiD74xaPo4yn81gmQ@mail.gmail.com>
	<54A195B6.3020504@redhat.com>
Message-ID: <54A6B92A.4080006@redhat.com>


On 12/29/2014 12:56 PM, Rafael Benevides wrote:
> Hi all,
>
> I'm pleased to announce that we have now the second Java EE 7 feature 
> shown as a JBoss Developer Quickstart: JDF-769 - Create a JAX-RS 
> Client API Quickstart - 
> https://github.com/jboss-developer/jboss-sandbox-quickstarts/tree/master/jaxrs-client
>
> I believe that we will need to update the existing Java EE 6 
> "jax-rs-client" quickstart (EAP and Wildfly) to a name that makes more 
> sense like jaxrs-resteasyclient.
>
That makes total sense. Should we do this after JBoss EAP 6.4 ships when 
we update the GitHub branches?
> Thanks
>
>
> On 9/9/14 10:07, Arun Gupta wrote:
>> Thanks, now watching!
>>
>> On Tue, Sep 9, 2014 at 3:53 PM, Rafael Benevides 
>> <benevides at redhat.com <mailto:benevides at redhat.com>> wrote:
>>
>>     I create a ticket for each one of them in case some of you want
>>     to follow the progress.
>>
>>     - WebSocket server endpoint - https://issues.jboss.org/browse/JDF-765
>>     - Chunk style batch processing -
>>     https://issues.jboss.org/browse/JDF-766
>>     - Object-based JSON generation and Stream-based JSON consuming -
>>     https://issues.jboss.org/browse/JDF-767
>>     - ManagedExecutorService - https://issues.jboss.org/browse/JDF-768
>>     - JAX-RS Client API - https://issues.jboss.org/browse/JDF-769
>>
>>
>>     Em 9/9/14, 1:29, Arun Gupta escreveu:
>>>     Hi Rafael,
>>>
>>>     If you are looking for the top 5 features that should be
>>>     highlighted in Java EE 7, then they would be:
>>>
>>>     - WebSocket server endpoint
>>>     - Chunk style batch processing
>>>     - Object-based JSON generation and Stream-based JSON consuming
>>>     - ManagedExecutorService
>>>     - JAX-RS Client API
>>>
>>>     There are samples for each one of these at:
>>>
>>>     https://github.com/javaee-samples/javaee7-samples
>>>
>>>     I had some basic discussions with Vineet last week on where some
>>>     of these usecases can be incorporated in Ticket Monster. Please
>>>     keep me involved in the design of how TiMo is going to evolve
>>>     for Java EE 7 support. Some of the documents that would be very
>>>     useful from that process are:
>>>
>>>     - How to migrate an existing Java EE 6 application to EE 7 ?
>>>     This would be very useful to our customers as well.
>>>     - Compare LOC/deployment descriptors between the EE 6 and 7
>>>     versions. These would make nice graphs.
>>>     - Before/after code fragment for different pieces that were
>>>     migrated.
>>>     - What proprietary technologies were replaced with
>>>     standards-based when using EE 7
>>>
>>>     Cheers
>>>     Arun
>>>
>>>     On Mon, Sep 8, 2014 at 9:30 PM, Rafael Benevides
>>>     <benevides at redhat.com <mailto:benevides at redhat.com>> wrote:
>>>
>>>         Returning the discussion about JBoss Developer Material for
>>>         Java EE 7,
>>>
>>>         Arun,
>>>
>>>         Do you have the list of the 5 features/use cases/quickstarts
>>>         that we want to show, right?  Can you share it?
>>>
>>>         Thanks
>>>
>>>         Em 8/25/14, 9:25, Rafael Benevides escreveu:
>>>>         Hi All,
>>>>
>>>>         We're about to start the update process of JBoss Developer
>>>>         Materials to Java EE 7. But before put the hands on it I
>>>>         talked with Pete and we decided that it's better to bring
>>>>         this $subject to discussion with everyone on this list.
>>>>
>>>>         Ticket Monster already started to be updated
>>>>         https://issues.jboss.org/browse/JDF-754
>>>>
>>>>         Actually our jboss-eap-quickstarts have been updated to
>>>>         Java EE 7.0 on https://github.com/wildfly/quickstart.
>>>>         Anyway we still miss some Java EE 7 specific features/use
>>>>         cases on these quickstarts.
>>>>
>>>>         It seems that Arun Gupta has a list of about 5 features/use
>>>>         cases/quickstarts that we want to show. The idea is to have
>>>>         these Java EE 7 specific quickstarts to be available at
>>>>         www.jboss.org <http://www.jboss.org>
>>>>
>>>>         The main point that we should discuss are:
>>>>
>>>>         - What are those quickstarts/features?
>>>>         - Where will we host those Java EE 7 quickstarts?
>>>>         https://github.com/jboss-developer/jboss-sandbox-quickstarts ?
>>>>         - Paul Robinson,
>>>>
>>>>         Considering that the jboss-sandbox-quickstarts github
>>>>         structure, do you think that it could have any issues with
>>>>         it? Can we choose just specific quickstarts to be present
>>>>         at www.jboss.org <http://www.jboss.org>
>>>>
>>>>         Well,
>>>>
>>>>         This is just a starting point, so we can discuss about this
>>>>         update process until we have a detailed plan.
>>>>
>>>>         The Google docs with the plan is available at:
>>>>         https://docs.google.com/document/d/1n0uVG2rhDf1eSp0b4MhggdIxNa3cthnuWaj2OjBpxoY/edit
>>>>
>>>>
>>>>         -- 
>>>>
>>>>         *Rafael Benevides | Senior Software Engineer*
>>>>         JBoss Developer
>>>>         M: +55-61-9269-6576 <tel:%2B55-61-9269-6576>
>>>>
>>>>         Red Hat
>>>>
>>>>         Better technology. Faster innovation. Powered by community
>>>>         collaboration.
>>>>         See how it works at www.redhat.com <http://www.redhat.com/>
>>>>
>>>>         LinkedIn <http://www.linkedin.com/company/3258288> Youtube
>>>>         <https://www.youtube.com/redhatlatam>
>>>>
>>>>
>>>>         _______________________________________________
>>>>         jbossdeveloper mailing list
>>>>         jbossdeveloper at lists.jboss.org  <mailto:jbossdeveloper at lists.jboss.org>
>>>>         https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>
>>>
>>>         _______________________________________________
>>>         jbossdeveloper mailing list
>>>         jbossdeveloper at lists.jboss.org
>>>         <mailto:jbossdeveloper at lists.jboss.org>
>>>         https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>
>>>
>>>
>>>
>>>     -- 
>>>     http://blog.arungupta.me
>>>     http://twitter.com/arungupta
>>
>>
>>
>>
>> -- 
>> http://blog.arungupta.me
>> http://twitter.com/arungupta
>
>
>
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150102/59c31f50/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 4815 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150102/59c31f50/attachment-0001.jpe 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 597 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150102/59c31f50/attachment-0002.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 616 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150102/59c31f50/attachment-0003.png 

From benevides at redhat.com  Fri Jan  2 15:08:10 2015
From: benevides at redhat.com (Rafael Benevides)
Date: Fri, 02 Jan 2015 18:08:10 -0200
Subject: [jbossdeveloper] Update JBoss Developer Materials to Java EE 7
 - JAX-RS Client API
In-Reply-To: <54A6B92A.4080006@redhat.com>
References: <53FB2B23.6090802@redhat.com>	<540DF5BC.3020103@redhat.com>	<CAGBoHQU93pCyWnJVrXE+FS9xT166JSbQUag2YANRcJfByBRqJg@mail.gmail.com>	<540EF853.9080405@redhat.com>	<CAGBoHQVoM6vgDnppe3MGCywtQN6Uxjg8zFiD74xaPo4yn81gmQ@mail.gmail.com>
	<54A195B6.3020504@redhat.com> <54A6B92A.4080006@redhat.com>
Message-ID: <54A6FAAA.4000101@redhat.com>


On 1/2/15 13:28, Sande Gilda wrote:
>
> On 12/29/2014 12:56 PM, Rafael Benevides wrote:
>> Hi all,
>>
>> I'm pleased to announce that we have now the second Java EE 7 feature 
>> shown as a JBoss Developer Quickstart: JDF-769 - Create a JAX-RS 
>> Client API Quickstart - 
>> https://github.com/jboss-developer/jboss-sandbox-quickstarts/tree/master/jaxrs-client
>>
>> I believe that we will need to update the existing Java EE 6 
>> "jax-rs-client" quickstart (EAP and Wildfly) to a name that makes 
>> more sense like jaxrs-resteasyclient.
>>
> That makes total sense. Should we do this after JBoss EAP 6.4 ships 
> when we update the GitHub branches?

IMO, yes.
>> Thanks
>>
>>
>> On 9/9/14 10:07, Arun Gupta wrote:
>>> Thanks, now watching!
>>>
>>> On Tue, Sep 9, 2014 at 3:53 PM, Rafael Benevides 
>>> <benevides at redhat.com <mailto:benevides at redhat.com>> wrote:
>>>
>>>     I create a ticket for each one of them in case some of you want
>>>     to follow the progress.
>>>
>>>     - WebSocket server endpoint -
>>>     https://issues.jboss.org/browse/JDF-765
>>>     - Chunk style batch processing -
>>>     https://issues.jboss.org/browse/JDF-766
>>>     - Object-based JSON generation and Stream-based JSON consuming -
>>>     https://issues.jboss.org/browse/JDF-767
>>>     - ManagedExecutorService - https://issues.jboss.org/browse/JDF-768
>>>     - JAX-RS Client API - https://issues.jboss.org/browse/JDF-769
>>>
>>>
>>>     Em 9/9/14, 1:29, Arun Gupta escreveu:
>>>>     Hi Rafael,
>>>>
>>>>     If you are looking for the top 5 features that should be
>>>>     highlighted in Java EE 7, then they would be:
>>>>
>>>>     - WebSocket server endpoint
>>>>     - Chunk style batch processing
>>>>     - Object-based JSON generation and Stream-based JSON consuming
>>>>     - ManagedExecutorService
>>>>     - JAX-RS Client API
>>>>
>>>>     There are samples for each one of these at:
>>>>
>>>>     https://github.com/javaee-samples/javaee7-samples
>>>>
>>>>     I had some basic discussions with Vineet last week on where
>>>>     some of these usecases can be incorporated in Ticket Monster.
>>>>     Please keep me involved in the design of how TiMo is going to
>>>>     evolve for Java EE 7 support. Some of the documents that would
>>>>     be very useful from that process are:
>>>>
>>>>     - How to migrate an existing Java EE 6 application to EE 7 ?
>>>>     This would be very useful to our customers as well.
>>>>     - Compare LOC/deployment descriptors between the EE 6 and 7
>>>>     versions. These would make nice graphs.
>>>>     - Before/after code fragment for different pieces that were
>>>>     migrated.
>>>>     - What proprietary technologies were replaced with
>>>>     standards-based when using EE 7
>>>>
>>>>     Cheers
>>>>     Arun
>>>>
>>>>     On Mon, Sep 8, 2014 at 9:30 PM, Rafael Benevides
>>>>     <benevides at redhat.com <mailto:benevides at redhat.com>> wrote:
>>>>
>>>>         Returning the discussion about JBoss Developer Material for
>>>>         Java EE 7,
>>>>
>>>>         Arun,
>>>>
>>>>         Do you have the list of the 5 features/use
>>>>         cases/quickstarts that we want to show, right?  Can you
>>>>         share it?
>>>>
>>>>         Thanks
>>>>
>>>>         Em 8/25/14, 9:25, Rafael Benevides escreveu:
>>>>>         Hi All,
>>>>>
>>>>>         We're about to start the update process of JBoss Developer
>>>>>         Materials to Java EE 7. But before put the hands on it I
>>>>>         talked with Pete and we decided that it's better to bring
>>>>>         this $subject to discussion with everyone on this list.
>>>>>
>>>>>         Ticket Monster already started to be updated
>>>>>         https://issues.jboss.org/browse/JDF-754
>>>>>
>>>>>         Actually our jboss-eap-quickstarts have been updated to
>>>>>         Java EE 7.0 on https://github.com/wildfly/quickstart.
>>>>>         Anyway we still miss some Java EE 7 specific features/use
>>>>>         cases on these quickstarts.
>>>>>
>>>>>         It seems that Arun Gupta has a list of about 5
>>>>>         features/use cases/quickstarts that we want to show. The
>>>>>         idea is to have these Java EE 7 specific quickstarts to be
>>>>>         available at www.jboss.org <http://www.jboss.org>
>>>>>
>>>>>         The main point that we should discuss are:
>>>>>
>>>>>         - What are those quickstarts/features?
>>>>>         - Where will we host those Java EE 7 quickstarts?
>>>>>         https://github.com/jboss-developer/jboss-sandbox-quickstarts ?
>>>>>         - Paul Robinson,
>>>>>
>>>>>         Considering that the jboss-sandbox-quickstarts github
>>>>>         structure, do you think that it could have any issues with
>>>>>         it? Can we choose just specific quickstarts to be present
>>>>>         at www.jboss.org <http://www.jboss.org>
>>>>>
>>>>>         Well,
>>>>>
>>>>>         This is just a starting point, so we can discuss about
>>>>>         this update process until we have a detailed plan.
>>>>>
>>>>>         The Google docs with the plan is available at:
>>>>>         https://docs.google.com/document/d/1n0uVG2rhDf1eSp0b4MhggdIxNa3cthnuWaj2OjBpxoY/edit
>>>>>
>>>>>
>>>>>         -- 
>>>>>
>>>>>         *Rafael Benevides | Senior Software Engineer*
>>>>>         JBoss Developer
>>>>>         M: +55-61-9269-6576 <tel:%2B55-61-9269-6576>
>>>>>
>>>>>         Red Hat
>>>>>
>>>>>         Better technology. Faster innovation. Powered by community
>>>>>         collaboration.
>>>>>         See how it works at www.redhat.com <http://www.redhat.com/>
>>>>>
>>>>>         LinkedIn <http://www.linkedin.com/company/3258288> Youtube
>>>>>         <https://www.youtube.com/redhatlatam>
>>>>>
>>>>>
>>>>>         _______________________________________________
>>>>>         jbossdeveloper mailing list
>>>>>         jbossdeveloper at lists.jboss.org  <mailto:jbossdeveloper at lists.jboss.org>
>>>>>         https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>
>>>>
>>>>         _______________________________________________
>>>>         jbossdeveloper mailing list
>>>>         jbossdeveloper at lists.jboss.org
>>>>         <mailto:jbossdeveloper at lists.jboss.org>
>>>>         https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>>
>>>>
>>>>
>>>>
>>>>     -- 
>>>>     http://blog.arungupta.me
>>>>     http://twitter.com/arungupta
>>>
>>>
>>>
>>>
>>> -- 
>>> http://blog.arungupta.me
>>> http://twitter.com/arungupta
>>
>>
>>
>> _______________________________________________
>> jbossdeveloper mailing list
>> jbossdeveloper at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150102/b8911540/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 4815 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150102/b8911540/attachment-0001.jpe 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 597 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150102/b8911540/attachment-0002.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 616 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150102/b8911540/attachment-0003.png 

From paul.robinson at redhat.com  Mon Jan  5 05:57:36 2015
From: paul.robinson at redhat.com (Paul Robinson)
Date: Mon, 5 Jan 2015 10:57:36 +0000
Subject: [jbossdeveloper] New year gift! QSTools 1.5.0.Final released
In-Reply-To: <54A16294.5040500@redhat.com>
References: <54A16294.5040500@redhat.com>
Message-ID: <B7B8B8FB-B771-4ACF-AE6B-D85AB5AC4204@redhat.com>

Thanks Rafael!

In particular, it?s good to see the meta-data value length checks in place!

Paul.

> On 29 Dec 2014, at 14:17, Rafael Benevides <benevides at redhat.com> wrote:
> 
> We will begin 2015 with QSTools 1.5.0.Final.
> 
> Since 1.4.1.Final release we started a long running path to 1.5.0 and here are the changes/new features:
> 
> 
> - Updated all references from JDF to "JBoss Developer Materials"
> - Allow ArtifactIdNameChecker to be ignored
> - Make MavenCentralRepositoryChecker to be ignored as default
> - JDF-690 - Changed artifactId from maven-qstools-plugin to qstools <https://issues.jboss.org/browse/JDF-690>
> - JDF-762 - Implemented a new goal: qstools:repositories that allows <repository /> maintenance in pom.xml files <https://issues.jboss.org/browse/JDF-762>
> - JDF-786 - QSTools shows detailed information about its version in report <https://issues.jboss.org/browse/JDF-786>
> - JDF-788 - Check Readme metadata value lenght <https://issues.jboss.org/browse/JDF-788> 
> 
> More details about setup "approved repositories" can see at http://jboss-developer.github.io/maven-qstools-plugin/#setup-jboss-maven-approved-repositories <http://jboss-developer.github.io/maven-qstools-plugin/#setup-jboss-maven-approved-repositories>
> 
> Happy new year!
> 
> - 
> -- 
> 
> Rafael Benevides | Senior Software Engineer
> JBoss Developer
> M: +55-61-9269-6576
> 
> <{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg>
> 
> Better technology. Faster innovation. Powered by community collaboration. 
> See how it works at www.redhat.com <http://www.redhat.com/> 
> 
> <linkedin.png> <http://www.linkedin.com/company/3258288> <youtube.png> <https://www.youtube.com/redhatlatam>_______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper


Paul.

-- 
Paul Robinson
JBoss Developer Team Lead (www.jboss.org)

Free/busy info: https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London

JBoss, a Division of Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150105/ac06103f/attachment.html 

From paul.robinson at redhat.com  Mon Jan  5 06:31:55 2015
From: paul.robinson at redhat.com (Paul Robinson)
Date: Mon, 5 Jan 2015 11:31:55 +0000
Subject: [jbossdeveloper] JBoss Developer production builds down over
	holiday period
In-Reply-To: <B038DEB5-AC1D-4149-9CF1-885F3B37645C@redhat.com>
References: <B038DEB5-AC1D-4149-9CF1-885F3B37645C@redhat.com>
Message-ID: <AD273EB7-8868-487A-ACAF-7CC1EF15E7B4@redhat.com>

FYI,

JBoss Developer site builds are back on.

Paul.

> On 19 Dec 2014, at 15:43, Paul Robinson <paul.robinson at redhat.com> wrote:
> 
> All,
> 
> Given that most of us are away for the next two weeks, we thought it best not to rebuild+publish the JBoss Developer production site every 6 hours, like we currently do. Should something go wrong it is unlikely that we would notice, plus I don?t really want to be on-call to fix it ;-)
> 
> I?ll re-enable on January the 5th.
> 
> Paul.
> 
> -- 
> Paul Robinson
> JBoss Developer Team Lead (www.jboss.org <http://www.jboss.org/>)
> 
> Free/busy info: https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London <https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London>
> 
> JBoss, a Division of Red Hat
> Registered in England and Wales under Company Registration No. 03798903
> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)
> 
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper


Paul.

-- 
Paul Robinson
JBoss Developer Team Lead (www.jboss.org)

Free/busy info: https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London

JBoss, a Division of Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150105/5b4a8724/attachment.html 

From paul.robinson at redhat.com  Wed Jan  7 05:29:13 2015
From: paul.robinson at redhat.com (Paul Robinson)
Date: Wed, 7 Jan 2015 10:29:13 +0000
Subject: [jbossdeveloper] Updating quickstarts documentation between releases
Message-ID: <705F5D1A-1E93-455E-92F3-3214A830C01A@redhat.com>

Paul,

I think you are the right person for this, but I could be wrong?

On JBoss Developer we index quickstarts for each product and render some of the documentation (README.md, CONTRIBUTING.md, for example) on the site. Here?s an example:http://www.jboss.org/quickstarts/eap/contributing/ <http://www-stg.jboss.org/pr/714/build/1464/quickstarts/eap/contributing/>. We index the latest release of each quickstart from the related Quickstart repo in the JBoss Developer GitHub organisation. It?s important that we index the release, as we know it has been QA?d against the latest product GA on the site.

However, there are several cases where broken links exist in the documentation that we are indexing. Notice the ?Fork? link on http://www.jboss.org/quickstarts/eap/contributing/ <http://www.jboss.org/quickstarts/eap/contributing/>. This is due to a broken link in the source content: https://github.com/jboss-developer/jboss-eap-quickstarts/blob/6.3.0.GA/CONTRIBUTING.md <https://github.com/jboss-developer/jboss-eap-quickstarts/blob/6.3.0.GA/CONTRIBUTING.md>. This is easy to fix at source, but we would need to wait for the next quickstarts release (in this case EAP 6.4.0.GA) before JBoss Developer can consume the fix. Broken links are bad for user experience and adversely affect SEO, so we?d rather get them fixed sooner. 

One solution would be to allow documentation only changes to be made to quickstarts between releases. In the example above, we would create a commit (fixing the broken link) on top of the 6.3.0.GA release (https://github.com/jboss-developer/jboss-eap-quickstarts/releases/tag/6.3.0.GA <https://github.com/jboss-developer/jboss-eap-quickstarts/releases/tag/6.3.0.GA>) and then tag it as a new release. I think we?d have to use some naming convention to indicate it was just docs that changed. JBoss Developer would then index the new tag in order to consume the fix. 

Is this the right thing to do?

Paul.

-- 
Paul Robinson
JBoss Developer Team Lead (www.jboss.org)

Free/busy info: https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London

JBoss, a Division of Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150107/af1ac5ba/attachment-0001.html 

From sgilda at redhat.com  Wed Jan  7 09:33:27 2015
From: sgilda at redhat.com (Sande Gilda)
Date: Wed, 07 Jan 2015 09:33:27 -0500
Subject: [jbossdeveloper] Updating quickstarts documentation between
	releases
In-Reply-To: <705F5D1A-1E93-455E-92F3-3214A830C01A@redhat.com>
References: <705F5D1A-1E93-455E-92F3-3214A830C01A@redhat.com>
Message-ID: <54AD43B7.3090705@redhat.com>


On 01/07/2015 05:29 AM, Paul Robinson wrote:
> Paul,
>
> I think you are the right person for this, but I could be wrong?
>
> On JBoss Developer we index quickstarts for each product and render 
> some of the documentation (README.md, CONTRIBUTING.md, for example) on 
> the site. Here?s an 
> example:http://www.jboss.org/quickstarts/eap/contributing/ 
> <http://www-stg.jboss.org/pr/714/build/1464/quickstarts/eap/contributing/>. 
> We index the latest release of each quickstart from the related 
> Quickstart repo in the JBoss Developer GitHub organisation. It?s 
> important that we index the release, as we know it has been QA?d 
> against the latest product GA on the site.
>
> However, there are several cases where broken links exist in the 
> documentation that we are indexing. Notice the ?Fork? link on 
> http://www.jboss.org/quickstarts/eap/contributing/. This is due to a 
> broken link in the source content: 
> https://github.com/jboss-developer/jboss-eap-quickstarts/blob/6.3.0.GA/CONTRIBUTING.md. 
> This is easy to fix at source, but we would need to wait for the next 
> quickstarts release (in this case EAP 6.4.0.GA) before JBoss Developer 
> can consume the fix. Broken links are bad for user experience and 
> adversely affect SEO, so we?d rather get them fixed sooner.
>
The CONTRIBUTING guide was moved to a common location to make it easier 
to maintain and share across products: 
https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONTRIBUTING.md

I moved quite a few files to the common location to make updates easier. 
The list is here: 
https://github.com/jboss-developer/jboss-developer-shared-resources/tree/master/guides

Since this file doesn't ship with a product, we can update it as needed.
> One solution would be to allow documentation only changes to be made 
> to quickstarts between releases. In the example above, we would create 
> a commit (fixing the broken link) on top of the 6.3.0.GA release 
> (https://github.com/jboss-developer/jboss-eap-quickstarts/releases/tag/6.3.0.GA) 
> and then tag it as a new release. I think we?d have to use some naming 
> convention to indicate it was just docs that changed. JBoss Developer 
> would then index the new tag in order to consume the fix.
Should we create a new branch for these issues, for example, 
6.3.1-develop and 6.3.1? Is it possible to create a new quickstart 
distribution after GA?
>
> Is this the right thing to do?
>
> Paul.
>
> -- 
> Paul Robinson
> JBoss Developer Team Lead (www.jboss.org <http://www.jboss.org>)
>
> Free/busy info: 
> https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London
>
> JBoss, a Division of Red Hat
> Registered in England and Wales under Company Registration No. 03798903
> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson 
> (US), Paul Hickey (Ireland)
>
>
>
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150107/077d76b0/attachment.html 

From pgier at redhat.com  Mon Jan 12 23:27:43 2015
From: pgier at redhat.com (Paul Gier)
Date: Mon, 12 Jan 2015 22:27:43 -0600
Subject: [jbossdeveloper] Updating quickstarts documentation between
	releases
In-Reply-To: <54AD43B7.3090705@redhat.com>
References: <705F5D1A-1E93-455E-92F3-3214A830C01A@redhat.com>
	<54AD43B7.3090705@redhat.com>
Message-ID: <54B49EBF.90703@redhat.com>

On 01/07/2015 08:33 AM, Sande Gilda wrote:
> 
> On 01/07/2015 05:29 AM, Paul Robinson wrote:
>> Paul,
>>
>> I think you are the right person for this, but I could be wrong?
>>
>> On JBoss Developer we index quickstarts for each product and render
>> some of the documentation (README.md, CONTRIBUTING.md, for example) on
>> the site. Here?s an
>> example:http://www.jboss.org/quickstarts/eap/contributing/
>> <http://www-stg.jboss.org/pr/714/build/1464/quickstarts/eap/contributing/>.
>> We index the latest release of each quickstart from the related
>> Quickstart repo in the JBoss Developer GitHub organisation. It?s
>> important that we index the release, as we know it has been QA?d
>> against the latest product GA on the site.
>>
>> However, there are several cases where broken links exist in the
>> documentation that we are indexing. Notice the ?Fork? link
>> on http://www.jboss.org/quickstarts/eap/contributing/. This is due to
>> a broken link in the source
>> content: https://github.com/jboss-developer/jboss-eap-quickstarts/blob/6.3.0.GA/CONTRIBUTING.md.
>> This is easy to fix at source, but we would need to wait for the next
>> quickstarts release (in this case EAP 6.4.0.GA) before JBoss Developer
>> can consume the fix. Broken links are bad for user experience and
>> adversely affect SEO, so we?d rather get them fixed sooner. 
>>
> The CONTRIBUTING guide was moved to a common location to make it easier
> to maintain and share across products:
> https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONTRIBUTING.md
> 
> I moved quite a few files to the common location to make updates easier.
> The list is here:
> https://github.com/jboss-developer/jboss-developer-shared-resources/tree/master/guides
> 
> Since this file doesn't ship with a product, we can update it as needed.
>> One solution would be to allow documentation only changes to be made
>> to quickstarts between releases. In the example above, we would create
>> a commit (fixing the broken link) on top of the 6.3.0.GA release
>> (https://github.com/jboss-developer/jboss-eap-quickstarts/releases/tag/6.3.0.GA)
>> and then tag it as a new release. I think we?d have to use some naming
>> convention to indicate it was just docs that changed. JBoss Developer
>> would then index the new tag in order to consume the fix.
> Should we create a new branch for these issues, for example,
> 6.3.1-develop and 6.3.1? Is it possible to create a new quickstart
> distribution after GA?

It's probably up to QA and PM whether we want to deliver an updated zip
with the patch stream (6.3.x).  I think we don't do it now just because
they don't want the extra effort of testing it.  I think we're pretty
much free to do what we want in the git repo, so we could create a
maintenance branch, although I'm not sure how we share that with the
customers.

>>
>> Is this the right thing to do?
>>
>> Paul.
>>
>> -- 
>> Paul Robinson
>> JBoss Developer Team Lead (www.jboss.org <http://www.jboss.org>)
>>
>> Free/busy
>> info: https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London
>>
>> JBoss, a Division of Red Hat
>> Registered in England and Wales under Company Registration No. 03798903
>> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson
>> (US), Paul Hickey (Ireland)
>>
>>
>>
>> _______________________________________________
>> jbossdeveloper mailing list
>> jbossdeveloper at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
> 

From paul.robinson at redhat.com  Tue Jan 13 03:36:01 2015
From: paul.robinson at redhat.com (Paul Robinson)
Date: Tue, 13 Jan 2015 08:36:01 +0000
Subject: [jbossdeveloper] Updating quickstarts documentation between
	releases
In-Reply-To: <54B49EBF.90703@redhat.com>
References: <705F5D1A-1E93-455E-92F3-3214A830C01A@redhat.com>
	<54AD43B7.3090705@redhat.com> <54B49EBF.90703@redhat.com>
Message-ID: <7E48CC0E-C28B-4944-94DE-64394F3EB078@redhat.com>


> On 13 Jan 2015, at 04:27, Paul Gier <pgier at redhat.com <mailto:pgier at redhat.com>> wrote:
> 
> On 01/07/2015 08:33 AM, Sande Gilda wrote:
>> 
>> On 01/07/2015 05:29 AM, Paul Robinson wrote:
>>> Paul,
>>> 
>>> I think you are the right person for this, but I could be wrong?
>>> 
>>> On JBoss Developer we index quickstarts for each product and render
>>> some of the documentation (README.md, CONTRIBUTING.md, for example) on
>>> the site. Here?s an
>>> example:http://www.jboss.org/quickstarts/eap/contributing/ <http://www.jboss.org/quickstarts/eap/contributing/>
>>> <http://www-stg.jboss.org/pr/714/build/1464/quickstarts/eap/contributing/ <http://www-stg.jboss.org/pr/714/build/1464/quickstarts/eap/contributing/>>.
>>> We index the latest release of each quickstart from the related
>>> Quickstart repo in the JBoss Developer GitHub organisation. It?s
>>> important that we index the release, as we know it has been QA?d
>>> against the latest product GA on the site.
>>> 
>>> However, there are several cases where broken links exist in the
>>> documentation that we are indexing. Notice the ?Fork? link
>>> on http://www.jboss.org/quickstarts/eap/contributing/ <http://www.jboss.org/quickstarts/eap/contributing/>. This is due to
>>> a broken link in the source
>>> content: https://github.com/jboss-developer/jboss-eap-quickstarts/blob/6.3.0.GA/CONTRIBUTING.md <https://github.com/jboss-developer/jboss-eap-quickstarts/blob/6.3.0.GA/CONTRIBUTING.md>.
>>> This is easy to fix at source, but we would need to wait for the next
>>> quickstarts release (in this case EAP 6.4.0.GA) before JBoss Developer
>>> can consume the fix. Broken links are bad for user experience and
>>> adversely affect SEO, so we?d rather get them fixed sooner. 
>>> 
>> The CONTRIBUTING guide was moved to a common location to make it easier
>> to maintain and share across products:
>> https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONTRIBUTING.md <https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONTRIBUTING.md>
>> 
>> I moved quite a few files to the common location to make updates easier.
>> The list is here:
>> https://github.com/jboss-developer/jboss-developer-shared-resources/tree/master/guides
>> 
>> Since this file doesn't ship with a product, we can update it as needed.
>>> One solution would be to allow documentation only changes to be made
>>> to quickstarts between releases. In the example above, we would create
>>> a commit (fixing the broken link) on top of the 6.3.0.GA release
>>> (https://github.com/jboss-developer/jboss-eap-quickstarts/releases/tag/6.3.0.GA)
>>> and then tag it as a new release. I think we?d have to use some naming
>>> convention to indicate it was just docs that changed. JBoss Developer
>>> would then index the new tag in order to consume the fix.
>> Should we create a new branch for these issues, for example,
>> 6.3.1-develop and 6.3.1? Is it possible to create a new quickstart
>> distribution after GA?
> 
> It's probably up to QA and PM whether we want to deliver an updated zip
> with the patch stream (6.3.x).  I think we don't do it now just because
> they don't want the extra effort of testing it. I think we're pretty
> much free to do what we want in the git repo, so we could create a
> maintenance branch, although I'm not sure how we share that with the
> customers.

So how about we limit these changes to just documentation (no code fixes) and only to critical items like broken links. We make the changes in the JBoss Developer GitHub repo and consume these changes on the JBoss Developer site.

QA and PM can ship these updated QS if they want, with the patch releases of the product.

Customers can go to JBoss Developer for the latest fixes to the QS docs. If they really want a new release, that?s gone through QA, then they would need to take that up with whoever manages their contract (not sure on the process for that, but hopefully you get my point).


> 
>>> 
>>> Is this the right thing to do?
>>> 
>>> Paul.
>>> 
>>> -- 
>>> Paul Robinson
>>> JBoss Developer Team Lead (www.jboss.org <http://www.jboss.org/> <http://www.jboss.org <http://www.jboss.org/>>)
>>> 
>>> Free/busy
>>> info: https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London <https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London>
>>> 
>>> JBoss, a Division of Red Hat
>>> Registered in England and Wales under Company Registration No. 03798903
>>> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson
>>> (US), Paul Hickey (Ireland)
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> jbossdeveloper mailing list
>>> jbossdeveloper at lists.jboss.org <mailto:jbossdeveloper at lists.jboss.org>
>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper


Paul.

-- 
Paul Robinson
JBoss Developer Team Lead (www.jboss.org <http://www.jboss.org/>)

Free/busy info: https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London <https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London>

JBoss, a Division of Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150113/a52c2441/attachment-0001.html 

From pgier at redhat.com  Wed Jan 14 11:08:44 2015
From: pgier at redhat.com (Paul Gier)
Date: Wed, 14 Jan 2015 10:08:44 -0600
Subject: [jbossdeveloper] Updating quickstarts documentation between
	releases
In-Reply-To: <7E48CC0E-C28B-4944-94DE-64394F3EB078@redhat.com>
References: <705F5D1A-1E93-455E-92F3-3214A830C01A@redhat.com>
	<54AD43B7.3090705@redhat.com> <54B49EBF.90703@redhat.com>
	<7E48CC0E-C28B-4944-94DE-64394F3EB078@redhat.com>
Message-ID: <54B6948C.4000409@redhat.com>

On 01/13/2015 02:36 AM, Paul Robinson wrote:
> 
>> On 13 Jan 2015, at 04:27, Paul Gier <pgier at redhat.com
>> <mailto:pgier at redhat.com>> wrote:
>>
>> On 01/07/2015 08:33 AM, Sande Gilda wrote:
>>>
>>> On 01/07/2015 05:29 AM, Paul Robinson wrote:
>>>> Paul,
>>>>
>>>> I think you are the right person for this, but I could be wrong?
>>>>
>>>> On JBoss Developer we index quickstarts for each product and render
>>>> some of the documentation (README.md, CONTRIBUTING.md, for example) on
>>>> the site. Here?s an
>>>> example:http://www.jboss.org/quickstarts/eap/contributing/
>>>> <http://www.jboss.org/quickstarts/eap/contributing/>
>>>> <http://www-stg.jboss.org/pr/714/build/1464/quickstarts/eap/contributing/>.
>>>> We index the latest release of each quickstart from the related
>>>> Quickstart repo in the JBoss Developer GitHub organisation. It?s
>>>> important that we index the release, as we know it has been QA?d
>>>> against the latest product GA on the site.
>>>>
>>>> However, there are several cases where broken links exist in the
>>>> documentation that we are indexing. Notice the ?Fork? link
>>>> on http://www.jboss.org/quickstarts/eap/contributing/. This is due to
>>>> a broken link in the source
>>>> content:
>>>> https://github.com/jboss-developer/jboss-eap-quickstarts/blob/6.3.0.GA/CONTRIBUTING.md.
>>>> This is easy to fix at source, but we would need to wait for the next
>>>> quickstarts release (in this case EAP 6.4.0.GA) before JBoss Developer
>>>> can consume the fix. Broken links are bad for user experience and
>>>> adversely affect SEO, so we?d rather get them fixed sooner. 
>>>>
>>> The CONTRIBUTING guide was moved to a common location to make it easier
>>> to maintain and share across products:
>>> https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONTRIBUTING.md
>>>
>>> I moved quite a few files to the common location to make updates easier.
>>> The list is here:
>>> https://github.com/jboss-developer/jboss-developer-shared-resources/tree/master/guides
>>>
>>> Since this file doesn't ship with a product, we can update it as needed.
>>>> One solution would be to allow documentation only changes to be made
>>>> to quickstarts between releases. In the example above, we would create
>>>> a commit (fixing the broken link) on top of the 6.3.0.GA release
>>>> (https://github.com/jboss-developer/jboss-eap-quickstarts/releases/tag/6.3.0.GA)
>>>> and then tag it as a new release. I think we?d have to use some naming
>>>> convention to indicate it was just docs that changed. JBoss Developer
>>>> would then index the new tag in order to consume the fix.
>>> Should we create a new branch for these issues, for example,
>>> 6.3.1-develop and 6.3.1? Is it possible to create a new quickstart
>>> distribution after GA?
>>
>> It's probably up to QA and PM whether we want to deliver an updated zip
>> with the patch stream (6.3.x).  I think we don't do it now just because
>> they don't want the extra effort of testing it. I think we're pretty
>> much free to do what we want in the git repo, so we could create a
>> maintenance branch, although I'm not sure how we share that with the
>> customers.
> 
> So how about we limit these changes to just documentation (no code
> fixes) and only to critical items like broken links. We make the changes
> in the JBoss Developer GitHub repo and consume these changes on the
> JBoss Developer site.
> 
> QA and PM can ship these updated QS if they want, with the patch
> releases of the product.
> 
> Customers can go to JBoss Developer for the latest fixes to the QS docs.
> If they really want a new release, that?s gone through QA, then they
> would need to take that up with whoever manages their contract (not sure
> on the process for that, but hopefully you get my point).
> 

That's fine with me.

> 
>>
>>>>
>>>> Is this the right thing to do?
>>>>
>>>> Paul.
>>>>
>>>> -- 
>>>> Paul Robinson
>>>> JBoss Developer Team Lead (www.jboss.org
>>>> <http://www.jboss.org/> <http://www.jboss.org <http://www.jboss.org/>>)
>>>>
>>>> Free/busy
>>>> info:
>>>> https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London
>>>>
>>>> JBoss, a Division of Red Hat
>>>> Registered in England and Wales under Company Registration No. 03798903
>>>> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson
>>>> (US), Paul Hickey (Ireland)
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> jbossdeveloper mailing list
>>>> jbossdeveloper at lists.jboss.org <mailto:jbossdeveloper at lists.jboss.org>
>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
> 
> 
> Paul.
> 
> -- 
> Paul Robinson
> JBoss Developer Team Lead (www.jboss.org <http://www.jboss.org>)
> 
> Free/busy
> info: https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London
> 
> JBoss, a Division of Red Hat
> Registered in England and Wales under Company Registration No. 03798903
> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson
> (US), Paul Hickey (Ireland)
> 

From paul.robinson at redhat.com  Wed Jan 14 11:52:14 2015
From: paul.robinson at redhat.com (Paul Robinson)
Date: Wed, 14 Jan 2015 16:52:14 +0000
Subject: [jbossdeveloper] Updating quickstarts documentation between
	releases
In-Reply-To: <54B6948C.4000409@redhat.com>
References: <705F5D1A-1E93-455E-92F3-3214A830C01A@redhat.com>
	<54AD43B7.3090705@redhat.com> <54B49EBF.90703@redhat.com>
	<7E48CC0E-C28B-4944-94DE-64394F3EB078@redhat.com>
	<54B6948C.4000409@redhat.com>
Message-ID: <DC5D03A5-19B6-49A4-8E43-898322BA0E52@redhat.com>


> On 14 Jan 2015, at 16:08, Paul Gier <pgier at redhat.com> wrote:
> 
> On 01/13/2015 02:36 AM, Paul Robinson wrote:
>> 
>>> On 13 Jan 2015, at 04:27, Paul Gier <pgier at redhat.com
>>> <mailto:pgier at redhat.com>> wrote:
>>> 
>>> On 01/07/2015 08:33 AM, Sande Gilda wrote:
>>>> 
>>>> On 01/07/2015 05:29 AM, Paul Robinson wrote:
>>>>> Paul,
>>>>> 
>>>>> I think you are the right person for this, but I could be wrong?
>>>>> 
>>>>> On JBoss Developer we index quickstarts for each product and render
>>>>> some of the documentation (README.md, CONTRIBUTING.md, for example) on
>>>>> the site. Here?s an
>>>>> example:http://www.jboss.org/quickstarts/eap/contributing/
>>>>> <http://www.jboss.org/quickstarts/eap/contributing/>
>>>>> <http://www-stg.jboss.org/pr/714/build/1464/quickstarts/eap/contributing/>.
>>>>> We index the latest release of each quickstart from the related
>>>>> Quickstart repo in the JBoss Developer GitHub organisation. It?s
>>>>> important that we index the release, as we know it has been QA?d
>>>>> against the latest product GA on the site.
>>>>> 
>>>>> However, there are several cases where broken links exist in the
>>>>> documentation that we are indexing. Notice the ?Fork? link
>>>>> on http://www.jboss.org/quickstarts/eap/contributing/. This is due to
>>>>> a broken link in the source
>>>>> content:
>>>>> https://github.com/jboss-developer/jboss-eap-quickstarts/blob/6.3.0.GA/CONTRIBUTING.md.
>>>>> This is easy to fix at source, but we would need to wait for the next
>>>>> quickstarts release (in this case EAP 6.4.0.GA) before JBoss Developer
>>>>> can consume the fix. Broken links are bad for user experience and
>>>>> adversely affect SEO, so we?d rather get them fixed sooner. 
>>>>> 
>>>> The CONTRIBUTING guide was moved to a common location to make it easier
>>>> to maintain and share across products:
>>>> https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONTRIBUTING.md
>>>> 
>>>> I moved quite a few files to the common location to make updates easier.
>>>> The list is here:
>>>> https://github.com/jboss-developer/jboss-developer-shared-resources/tree/master/guides
>>>> 
>>>> Since this file doesn't ship with a product, we can update it as needed.
>>>>> One solution would be to allow documentation only changes to be made
>>>>> to quickstarts between releases. In the example above, we would create
>>>>> a commit (fixing the broken link) on top of the 6.3.0.GA release
>>>>> (https://github.com/jboss-developer/jboss-eap-quickstarts/releases/tag/6.3.0.GA)
>>>>> and then tag it as a new release. I think we?d have to use some naming
>>>>> convention to indicate it was just docs that changed. JBoss Developer
>>>>> would then index the new tag in order to consume the fix.
>>>> Should we create a new branch for these issues, for example,
>>>> 6.3.1-develop and 6.3.1? Is it possible to create a new quickstart
>>>> distribution after GA?
>>> 
>>> It's probably up to QA and PM whether we want to deliver an updated zip
>>> with the patch stream (6.3.x).  I think we don't do it now just because
>>> they don't want the extra effort of testing it. I think we're pretty
>>> much free to do what we want in the git repo, so we could create a
>>> maintenance branch, although I'm not sure how we share that with the
>>> customers.
>> 
>> So how about we limit these changes to just documentation (no code
>> fixes) and only to critical items like broken links. We make the changes
>> in the JBoss Developer GitHub repo and consume these changes on the
>> JBoss Developer site.
>> 
>> QA and PM can ship these updated QS if they want, with the patch
>> releases of the product.
>> 
>> Customers can go to JBoss Developer for the latest fixes to the QS docs.
>> If they really want a new release, that?s gone through QA, then they
>> would need to take that up with whoever manages their contract (not sure
>> on the process for that, but hopefully you get my point).
>> 
> 
> That's fine with me.

Great. Does this need adding to some guidlines somewhere?

> 
>> 
>>> 
>>>>> 
>>>>> Is this the right thing to do?
>>>>> 
>>>>> Paul.
>>>>> 
>>>>> -- 
>>>>> Paul Robinson
>>>>> JBoss Developer Team Lead (www.jboss.org
>>>>> <http://www.jboss.org/> <http://www.jboss.org <http://www.jboss.org/>>)
>>>>> 
>>>>> Free/busy
>>>>> info:
>>>>> https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London
>>>>> 
>>>>> JBoss, a Division of Red Hat
>>>>> Registered in England and Wales under Company Registration No. 03798903
>>>>> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson
>>>>> (US), Paul Hickey (Ireland)
>>>>> 
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> jbossdeveloper mailing list
>>>>> jbossdeveloper at lists.jboss.org <mailto:jbossdeveloper at lists.jboss.org>
>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>> 
>> 
>> Paul.
>> 
>> -- 
>> Paul Robinson
>> JBoss Developer Team Lead (www.jboss.org <http://www.jboss.org>)
>> 
>> Free/busy
>> info: https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London
>> 
>> JBoss, a Division of Red Hat
>> Registered in England and Wales under Company Registration No. 03798903
>> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson
>> (US), Paul Hickey (Ireland)
>> 


Paul.

-- 
Paul Robinson
JBoss Developer Team Lead (www.jboss.org)

Free/busy info: https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London

JBoss, a Division of Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150114/ce41da4e/attachment.html 

From paul.robinson at redhat.com  Thu Jan 15 05:27:36 2015
From: paul.robinson at redhat.com (Paul Robinson)
Date: Thu, 15 Jan 2015 10:27:36 +0000
Subject: [jbossdeveloper] Pruning old data from the DCP
In-Reply-To: <993C010A-70C4-4000-BF7B-1E8CD3DB785D@redhat.com>
References: <AC5447D0-278A-4917-A2D1-9024A12A6F0F@redhat.com>
	<993C010A-70C4-4000-BF7B-1E8CD3DB785D@redhat.com>
Message-ID: <979F2071-AB4A-4360-9435-F1CB0783C101@redhat.com>

Lukas, Vlastimil,

Did you see this?

Paul.

> On 18 Dec 2014, at 13:11, Pete Muir <pmuir at redhat.com> wrote:
> 
> I think this proposal looks good, but it would be great to get e.g. Lukas, Vlastimil etc. to comment on it.
> 
>> On 18 Dec 2014, at 11:02, Paul Robinson <paul.robinson at redhat.com <mailto:paul.robinson at redhat.com>> wrote:
>> 
>> All,
>> 
>> I?ve put together a proposal for how to remove old data from the DCP: https://issues.jboss.org/browse/DEVELOPER-1164 <https://issues.jboss.org/browse/DEVELOPER-1164>
>> 
>> Essentially, we delete all JBoss Developer content that was not updated during the current production build.
>> 
>> Does this seem feasible? Am I missing something?
>> 
>> Paul.
>> 
>> -- 
>> Paul Robinson
>> JBoss Developer Team Lead (www.jboss.org <http://www.jboss.org/>)
>> 
>> Free/busy info: https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London <https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London>
>> 
>> JBoss, a Division of Red Hat
>> Registered in England and Wales under Company Registration No. 03798903
>> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)
>> 
>> _______________________________________________
>> jbossdeveloper mailing list
>> jbossdeveloper at lists.jboss.org <mailto:jbossdeveloper at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
> 


Paul.

-- 
Paul Robinson
JBoss Developer Team Lead (www.jboss.org)

Free/busy info: https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London

JBoss, a Division of Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150115/4bd475d9/attachment-0001.html 

From paul.robinson at redhat.com  Fri Jan 16 06:33:11 2015
From: paul.robinson at redhat.com (Paul Robinson)
Date: Fri, 16 Jan 2015 11:33:11 +0000
Subject: [jbossdeveloper] JBoss Developer's Technical Debt
Message-ID: <5B2BC9B2-1355-43B8-97F9-8C796FD4C1C0@redhat.com>

All,

I?m trying to collate a list of technical debt that we currently have. Google the term if you are not familiar. I want to work towards clearing this debt to make our development more efficient and the dev time happier :-)

I think we can use the term quite loosely. so if in doubt, add to the list! Here?s what I?ve got so far. Please can you have a think about this and add your items:

https://docs.google.com/a/redhat.com/document/d/1-VPbrrgZfR28Sz0XgHnV235E4sT9PhY8tEe9QvknVfQ/edit <https://docs.google.com/a/redhat.com/document/d/1-VPbrrgZfR28Sz0XgHnV235E4sT9PhY8tEe9QvknVfQ/edit>

Thanks,

Paul.

-- 
Paul Robinson
JBoss Developer Team Lead (www.jboss.org)

Free/busy info: https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London

JBoss, a Division of Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150116/4f73dc72/attachment.html 

From benevides at redhat.com  Mon Jan 19 12:03:17 2015
From: benevides at redhat.com (Rafael Benevides)
Date: Mon, 19 Jan 2015 12:03:17 -0500
Subject: [jbossdeveloper] JBoss Developer's Technical Debt
In-Reply-To: <5B2BC9B2-1355-43B8-97F9-8C796FD4C1C0@redhat.com>
References: <5B2BC9B2-1355-43B8-97F9-8C796FD4C1C0@redhat.com>
Message-ID: <54BD38D5.80107@redhat.com>

You listed everything that came to my mind :)

On 1/16/15 06:33, Paul Robinson wrote:
> All,
>
> I?m trying to collate a list of technical debt that we currently have. 
> Google the term if you are not familiar. I want to work towards 
> clearing this debt to make our development more efficient and the dev 
> time happier :-)
>
> I think we can use the term quite loosely. so if in doubt, add to the 
> list! Here?s what I?ve got so far. Please can you have a think about 
> this and add your items:
>
> https://docs.google.com/a/redhat.com/document/d/1-VPbrrgZfR28Sz0XgHnV235E4sT9PhY8tEe9QvknVfQ/edit
>
> Thanks,
>
> Paul.
>
> -- 
> Paul Robinson
> JBoss Developer Team Lead (www.jboss.org <http://www.jboss.org>)
>
> Free/busy info: 
> https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London
>
> JBoss, a Division of Red Hat
> Registered in England and Wales under Company Registration No. 03798903
> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson 
> (US), Paul Hickey (Ireland)
>
>
>
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150119/b785dbe9/attachment.html 

From sgilda at redhat.com  Thu Jan 22 07:34:16 2015
From: sgilda at redhat.com (Sande Gilda)
Date: Thu, 22 Jan 2015 07:34:16 -0500
Subject: [jbossdeveloper] jboss.org download of JBoss EAP 6.4 beta
Message-ID: <54C0EE48.30203@redhat.com>

I have a documentation bug on my queue related to the green 'Download' 
button on the https://www.jboss.org/products/eap/overview page.

Will that link be updated to point to the JBoss EAP 6.4 beta when it 
ships, or would they have to choose 'Download JBoss EAP' to download the 
beta?

I assume it will definitely be updated to JBoss EAP 6.4 GA when it ships?

Thanks,
Sande

From paul.robinson at redhat.com  Thu Jan 22 15:07:45 2015
From: paul.robinson at redhat.com (Paul Robinson)
Date: Thu, 22 Jan 2015 20:07:45 +0000
Subject: [jbossdeveloper] jboss.org download of JBoss EAP 6.4 beta
In-Reply-To: <54C0EE48.30203@redhat.com>
References: <54C0EE48.30203@redhat.com>
Message-ID: <6EFFDEFF-57EA-42C8-B02F-B0DA6799D11B@redhat.com>

Sande,

The green button always links to the latest GA. So 6.3.0.GA now and 6.4.0.GA when it ships. The area underneath shows the latest pre-GA release, should one exist that, is newer than the latest GA.

Does that help clarify?

Paul.

> On 22 Jan 2015, at 12:34, Sande Gilda <sgilda at redhat.com> wrote:
> 
> I have a documentation bug on my queue related to the green 'Download' 
> button on the https://www.jboss.org/products/eap/overview page.
> 
> Will that link be updated to point to the JBoss EAP 6.4 beta when it 
> ships, or would they have to choose 'Download JBoss EAP' to download the 
> beta?
> 
> I assume it will definitely be updated to JBoss EAP 6.4 GA when it ships?
> 
> Thanks,
> Sande
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper


Paul.

-- 
Paul Robinson
JBoss Developer Team Lead (www.jboss.org)

Free/busy info: https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London

JBoss, a Division of Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150122/5af9bdd9/attachment.html 

From sgilda at redhat.com  Thu Jan 22 15:38:19 2015
From: sgilda at redhat.com (Sande Gilda)
Date: Thu, 22 Jan 2015 15:38:19 -0500
Subject: [jbossdeveloper] jboss.org download of JBoss EAP 6.4 beta
In-Reply-To: <6EFFDEFF-57EA-42C8-B02F-B0DA6799D11B@redhat.com>
References: <54C0EE48.30203@redhat.com>
	<6EFFDEFF-57EA-42C8-B02F-B0DA6799D11B@redhat.com>
Message-ID: <54C15FBB.3020909@redhat.com>

Thanks Paul!

Yes it does. QE is suggesting I change the documentation during beta, 
but then I would have to change it back. Maybe I'll just change it to 
explain the download button always downloads the latest GA and to use 
the other link to see the new pre-GA versions.

Thanks again,
Sande

On 01/22/2015 03:07 PM, Paul Robinson wrote:
> Sande,
>
> The green button always links to the latest GA. So 6.3.0.GA now and 
> 6.4.0.GA when it ships. The area underneath shows the latest pre-GA 
> release, should one exist that, is newer than the latest GA.
>
> Does that help clarify?
>
> Paul.
>
>> On 22 Jan 2015, at 12:34, Sande Gilda <sgilda at redhat.com 
>> <mailto:sgilda at redhat.com>> wrote:
>>
>> I have a documentation bug on my queue related to the green 'Download'
>> button on the https://www.jboss.org/products/eap/overview page.
>>
>> Will that link be updated to point to the JBoss EAP 6.4 beta when it
>> ships, or would they have to choose 'Download JBoss EAP' to download the
>> beta?
>>
>> I assume it will definitely be updated to JBoss EAP 6.4 GA when it ships?
>>
>> Thanks,
>> Sande
>> _______________________________________________
>> jbossdeveloper mailing list
>> jbossdeveloper at lists.jboss.org <mailto:jbossdeveloper at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>
>
> Paul.
>
> -- 
> Paul Robinson
> JBoss Developer Team Lead (www.jboss.org <http://www.jboss.org>)
>
> Free/busy info: 
> https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London
>
> JBoss, a Division of Red Hat
> Registered in England and Wales under Company Registration No. 03798903
> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson 
> (US), Paul Hickey (Ireland)
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150122/63f4aa15/attachment-0001.html 

From pmuir at redhat.com  Fri Jan 23 06:16:10 2015
From: pmuir at redhat.com (Pete Muir)
Date: Fri, 23 Jan 2015 11:16:10 +0000
Subject: [jbossdeveloper] jboss.org download of JBoss EAP 6.4 beta
In-Reply-To: <54C15FBB.3020909@redhat.com>
References: <54C0EE48.30203@redhat.com>
	<6EFFDEFF-57EA-42C8-B02F-B0DA6799D11B@redhat.com>
	<54C15FBB.3020909@redhat.com>
Message-ID: <58707538-CA12-42D4-A255-9754EF03DB46@redhat.com>

Agreed, document the UX, we won?t change it!

> On 22 Jan 2015, at 20:38, Sande Gilda <sgilda at redhat.com> wrote:
> 
> Thanks Paul!
> 
> Yes it does. QE is suggesting I change the documentation during beta, but then I would have to change it back. Maybe I'll just change it to explain the download button always downloads the latest GA and to use the other link to see the new pre-GA versions. 
> 
> Thanks again,
> Sande
> 
> On 01/22/2015 03:07 PM, Paul Robinson wrote:
>> Sande,
>> 
>> The green button always links to the latest GA. So 6.3.0.GA now and 6.4.0.GA when it ships. The area underneath shows the latest pre-GA release, should one exist that, is newer than the latest GA.
>> 
>> Does that help clarify?
>> 
>> Paul.
>> 
>>> On 22 Jan 2015, at 12:34, Sande Gilda <sgilda at redhat.com <mailto:sgilda at redhat.com>> wrote:
>>> 
>>> I have a documentation bug on my queue related to the green 'Download' 
>>> button on the https://www.jboss.org/products/eap/overview <https://www.jboss.org/products/eap/overview> page.
>>> 
>>> Will that link be updated to point to the JBoss EAP 6.4 beta when it 
>>> ships, or would they have to choose 'Download JBoss EAP' to download the 
>>> beta?
>>> 
>>> I assume it will definitely be updated to JBoss EAP 6.4 GA when it ships?
>>> 
>>> Thanks,
>>> Sande
>>> _______________________________________________
>>> jbossdeveloper mailing list
>>> jbossdeveloper at lists.jboss.org <mailto:jbossdeveloper at lists.jboss.org>
>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper <https://lists.jboss.org/mailman/listinfo/jbossdeveloper>
>> 
>> 
>> Paul.
>> 
>> -- 
>> Paul Robinson
>> JBoss Developer Team Lead (www.jboss.org <http://www.jboss.org/>)
>> 
>> Free/busy info: https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London <https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London>
>> 
>> JBoss, a Division of Red Hat
>> Registered in England and Wales under Company Registration No. 03798903
>> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)
>> 
> 
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150123/41f4e9d9/attachment.html 

From sgilda at redhat.com  Fri Jan 23 08:39:26 2015
From: sgilda at redhat.com (Sande Gilda)
Date: Fri, 23 Jan 2015 08:39:26 -0500
Subject: [jbossdeveloper] jboss.org download of JBoss EAP 6.4 beta
In-Reply-To: <58707538-CA12-42D4-A255-9754EF03DB46@redhat.com>
References: <54C0EE48.30203@redhat.com>
	<6EFFDEFF-57EA-42C8-B02F-B0DA6799D11B@redhat.com>
	<54C15FBB.3020909@redhat.com>
	<58707538-CA12-42D4-A255-9754EF03DB46@redhat.com>
Message-ID: <54C24F0E.5030004@redhat.com>

I wrote this doc early in the jboss.org development cycle. At that time, 
the installation program download wasn't available on jboss.org and the 
'Download' button downloaded the ZIP file. I had commented out the 
jboss.org installer instructions for that reason. I updated all of the 
instructions and it now covers both the ZIP and JAR downloads 
(accurately I hope).

Thanks all!

On 01/23/2015 06:16 AM, Pete Muir wrote:
> Agreed, document the UX, we won?t change it!
>
>> On 22 Jan 2015, at 20:38, Sande Gilda <sgilda at redhat.com 
>> <mailto:sgilda at redhat.com>> wrote:
>>
>> Thanks Paul!
>>
>> Yes it does. QE is suggesting I change the documentation during beta, 
>> but then I would have to change it back. Maybe I'll just change it to 
>> explain the download button always downloads the latest GA and to use 
>> the other link to see the new pre-GA versions.
>>
>> Thanks again,
>> Sande
>>
>> On 01/22/2015 03:07 PM, Paul Robinson wrote:
>>> Sande,
>>>
>>> The green button always links to the latest GA. So 6.3.0.GA now and 
>>> 6.4.0.GA when it ships. The area underneath shows the latest pre-GA 
>>> release, should one exist that, is newer than the latest GA.
>>>
>>> Does that help clarify?
>>>
>>> Paul.
>>>
>>>> On 22 Jan 2015, at 12:34, Sande Gilda <sgilda at redhat.com 
>>>> <mailto:sgilda at redhat.com>> wrote:
>>>>
>>>> I have a documentation bug on my queue related to the green 'Download'
>>>> button on the https://www.jboss.org/products/eap/overview page.
>>>>
>>>> Will that link be updated to point to the JBoss EAP 6.4 beta when it
>>>> ships, or would they have to choose 'Download JBoss EAP' to 
>>>> download the
>>>> beta?
>>>>
>>>> I assume it will definitely be updated to JBoss EAP 6.4 GA when it 
>>>> ships?
>>>>
>>>> Thanks,
>>>> Sande
>>>> _______________________________________________
>>>> jbossdeveloper mailing list
>>>> jbossdeveloper at lists.jboss.org <mailto:jbossdeveloper at lists.jboss.org>
>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>>
>>>
>>> Paul.
>>>
>>> -- 
>>> Paul Robinson
>>> JBoss Developer Team Lead (www.jboss.org <http://www.jboss.org/>)
>>>
>>> Free/busy info: 
>>> https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europe/London
>>>
>>> JBoss, a Division of Red Hat
>>> Registered in England and Wales under Company Registration No. 03798903
>>> Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson 
>>> (US), Paul Hickey (Ireland)
>>>
>>
>> _______________________________________________
>> jbossdeveloper mailing list
>> jbossdeveloper at lists.jboss.org <mailto:jbossdeveloper at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150123/af8aa1d1/attachment.html 

From benevides at redhat.com  Fri Jan 23 13:38:51 2015
From: benevides at redhat.com (Rafael Benevides)
Date: Fri, 23 Jan 2015 13:38:51 -0500
Subject: [jbossdeveloper] JBoss Developer Materials Owners
Message-ID: <54C2953B.2070806@redhat.com>

Hi all,

As JBoss Developer Materials keeps growing, sometimes it can be a hard 
task when it's needed to deal with many products and components.

To make easy to identify the person that should be contacted in case of 
any issues, the following MOJO Document: 
https://mojo.redhat.com/docs/DOC-1010716 have been created to make it 
ease to contact the right person in case of issues.

Please, take a look at the document and feel free to edit it in case you 
want to add/replace the person that should be contact. We also encourage 
Quickstarts/BOMs/Archetypes owners to join 
https://lists.jboss.org/mailman/listinfo/jbossdeveloper to keep them 
aware of latests discussion, news and guildeline updates.

Thanks so much!

-- 

*Rafael Benevides | Senior Software Engineer*
JBoss Developer
M: +55-61-9269-6576

Red Hat

Better technology. Faster innovation. Powered by community collaboration.
See how it works at www.redhat.com <http://www.redhat.com/>

LinkedIn <http://www.linkedin.com/company/3258288> Youtube 
<https://www.youtube.com/redhatlatam>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150123/2442bb6e/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: {a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg
Type: image/jpeg
Size: 4815 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150123/2442bb6e/attachment-0001.jpg 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: linkedin.png
Type: image/png
Size: 597 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150123/2442bb6e/attachment-0002.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: youtube.png
Type: image/png
Size: 616 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150123/2442bb6e/attachment-0003.png 

From mnovotny at redhat.com  Mon Jan 26 03:45:09 2015
From: mnovotny at redhat.com (Marek Novotny)
Date: Mon, 26 Jan 2015 09:45:09 +0100
Subject: [jbossdeveloper] New year gift! QSTools 1.5.0.Final released
In-Reply-To: <54A16294.5040500@redhat.com>
References: <54A16294.5040500@redhat.com>
Message-ID: <54C5FE95.9070802@redhat.com>

Hi Rafael,
 it seems the 1.5.0.Final release is  not synced to Maven Central.

On 29.12.2014 15:17, Rafael Benevides wrote:
> We will begin 2015 with QSTools 1.5.0.Final.
>
> Since 1.4.1.Final release we started a long running path to 1.5.0 and
> here are the changes/new features:
>
>
> - Updated all references from JDF to "JBoss Developer Materials"
> - Allow ArtifactIdNameChecker to be ignored
> - Make MavenCentralRepositoryChecker to be ignored as default
> - JDF-690 - Changed artifactId from maven-qstools-plugin to qstools
> <https://issues.jboss.org/browse/JDF-690>
> - JDF-762 - Implemented a new goal: qstools:repositories that allows
> <repository /> maintenance in pom.xml files
> <https://issues.jboss.org/browse/JDF-762>
> - JDF-786 - QSTools shows detailed information about its version in
> report <https://issues.jboss.org/browse/JDF-786>
> - JDF-788 - Check Readme metadata value lenght
> <https://issues.jboss.org/browse/JDF-788>
>
> More details about setup "approved repositories" can see at
> http://jboss-developer.github.io/maven-qstools-plugin/#setup-jboss-maven-approved-repositories
>
> Happy new year!
>
> -
> -- 
>
> *Rafael Benevides | Senior Software Engineer*
> JBoss Developer
> M: +55-61-9269-6576
>
> Red Hat
>
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at www.redhat.com <http://www.redhat.com/>
>
> LinkedIn <http://www.linkedin.com/company/3258288> Youtube
> <https://www.youtube.com/redhatlatam>
>
>
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper


-- 
Marek Novotny
--
WFK and Seam Product Lead

Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150126/8152b7b2/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 4815 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150126/8152b7b2/attachment.jpe 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 597 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150126/8152b7b2/attachment.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 616 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150126/8152b7b2/attachment-0001.png 

From benevides at redhat.com  Mon Jan 26 14:08:08 2015
From: benevides at redhat.com (Rafael Benevides)
Date: Mon, 26 Jan 2015 14:08:08 -0500
Subject: [jbossdeveloper] New year gift! QSTools 1.5.0.Final released
In-Reply-To: <54C5FE95.9070802@redhat.com>
References: <54A16294.5040500@redhat.com> <54C5FE95.9070802@redhat.com>
Message-ID: <54C69098.3020209@redhat.com>

It looks that it's available there 
http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.jboss.maven.plugins%22%20AND%20a%3A%22qstools%22

Are you having any issues ?

On 1/26/15 03:45, Marek Novotny wrote:
> Hi Rafael,
>  it seems the 1.5.0.Final release is  not synced to Maven Central.
>
> On 29.12.2014 15:17, Rafael Benevides wrote:
>> We will begin 2015 with QSTools 1.5.0.Final.
>>
>> Since 1.4.1.Final release we started a long running path to 1.5.0 and 
>> here are the changes/new features:
>>
>>
>> - Updated all references from JDF to "JBoss Developer Materials"
>> - Allow ArtifactIdNameChecker to be ignored
>> - Make MavenCentralRepositoryChecker to be ignored as default
>> - JDF-690 - Changed artifactId from maven-qstools-plugin to qstools 
>> <https://issues.jboss.org/browse/JDF-690>
>> - JDF-762 - Implemented a new goal: qstools:repositories that allows 
>> <repository /> maintenance in pom.xml files 
>> <https://issues.jboss.org/browse/JDF-762>
>> - JDF-786 - QSTools shows detailed information about its version in 
>> report <https://issues.jboss.org/browse/JDF-786>
>> - JDF-788 - Check Readme metadata value lenght 
>> <https://issues.jboss.org/browse/JDF-788>
>>
>> More details about setup "approved repositories" can see at 
>> http://jboss-developer.github.io/maven-qstools-plugin/#setup-jboss-maven-approved-repositories
>>
>> Happy new year!
>>
>> -
>> -- 
>>
>> *Rafael Benevides | Senior Software Engineer*
>> JBoss Developer
>> M: +55-61-9269-6576
>>
>> Red Hat
>>
>> Better technology. Faster innovation. Powered by community 
>> collaboration.
>> See how it works at www.redhat.com <http://www.redhat.com/>
>>
>> LinkedIn <http://www.linkedin.com/company/3258288> Youtube 
>> <https://www.youtube.com/redhatlatam>
>>
>>
>> _______________________________________________
>> jbossdeveloper mailing list
>> jbossdeveloper at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>
>
> -- 
> Marek Novotny
> --
> WFK and Seam Product Lead
>
> Red Hat Czech s.r.o.
> Purkynova 99
> 612 45 Brno
>
>
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150126/78534fca/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 4815 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150126/78534fca/attachment-0001.jpe 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 597 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150126/78534fca/attachment-0002.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 616 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150126/78534fca/attachment-0003.png 

From benevides at redhat.com  Tue Jan 27 00:09:56 2015
From: benevides at redhat.com (Rafael Benevides)
Date: Tue, 27 Jan 2015 00:09:56 -0500
Subject: [jbossdeveloper] JBoss Developer Materials Guidelines
Message-ID: <54C71DA4.9080009@redhat.com>

To make easy to people understand some constraints that are applied to  
JBoss Developer Materials (specially those which refers to Quickstarts 
and QSTools violations), I tried to summarize all Materials Guidelines 
on this document: https://mojo.redhat.com/docs/DOC-1008312 based on 
QSTools violations checkers.

I also included a section for Archetypes (with emphasis on quickstarts 
synchronization) and BOMs.

One of the objectives to have JBoss Developers Guidelines written 
somewhere is to have all different teams listed in 
https://mojo.redhat.com/docs/DOC-1010716 to follow the same guidelines

I hope you all enjoy!
-- 

*Rafael Benevides | Senior Software Engineer*
JBoss Developer
M: +55-61-9269-6576

Red Hat

Better technology. Faster innovation. Powered by community collaboration.
See how it works at www.redhat.com <http://www.redhat.com/>

LinkedIn <http://www.linkedin.com/company/3258288> Youtube 
<https://www.youtube.com/redhatlatam>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150127/1cf0e39b/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: {a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg
Type: image/jpeg
Size: 4815 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150127/1cf0e39b/attachment.jpg 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: linkedin.png
Type: image/png
Size: 597 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150127/1cf0e39b/attachment.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: youtube.png
Type: image/png
Size: 616 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150127/1cf0e39b/attachment-0001.png 

From mnovotny at redhat.com  Tue Jan 27 01:31:10 2015
From: mnovotny at redhat.com (Marek Novotny)
Date: Tue, 27 Jan 2015 07:31:10 +0100
Subject: [jbossdeveloper] New year gift! QSTools 1.5.0.Final released
In-Reply-To: <54C69098.3020209@redhat.com>
References: <54A16294.5040500@redhat.com> <54C5FE95.9070802@redhat.com>
	<54C69098.3020209@redhat.com>
Message-ID: <54C730AE.3040806@redhat.com>

Hmm, you changed artifactId that explains why only updating of string
version doesn't help.

On 26.1.2015 20:08, Rafael Benevides wrote:
> It looks that it's available there
> http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.jboss.maven.plugins%22%20AND%20a%3A%22qstools%22
>
> Are you having any issues ?
>
> On 1/26/15 03:45, Marek Novotny wrote:
>> Hi Rafael,
>>  it seems the 1.5.0.Final release is  not synced to Maven Central.
>>
>> On 29.12.2014 15:17, Rafael Benevides wrote:
>>> We will begin 2015 with QSTools 1.5.0.Final.
>>>
>>> Since 1.4.1.Final release we started a long running path to 1.5.0
>>> and here are the changes/new features:
>>>
>>>
>>> - Updated all references from JDF to "JBoss Developer Materials"
>>> - Allow ArtifactIdNameChecker to be ignored
>>> - Make MavenCentralRepositoryChecker to be ignored as default
>>> - JDF-690 - Changed artifactId from maven-qstools-plugin to qstools
>>> <https://issues.jboss.org/browse/JDF-690>
>>> - JDF-762 - Implemented a new goal: qstools:repositories that allows
>>> <repository /> maintenance in pom.xml files
>>> <https://issues.jboss.org/browse/JDF-762>
>>> - JDF-786 - QSTools shows detailed information about its version in
>>> report <https://issues.jboss.org/browse/JDF-786>
>>> - JDF-788 - Check Readme metadata value lenght
>>> <https://issues.jboss.org/browse/JDF-788>
>>>
>>> More details about setup "approved repositories" can see at
>>> http://jboss-developer.github.io/maven-qstools-plugin/#setup-jboss-maven-approved-repositories
>>>
>>> Happy new year!
>>>
>>> -
>>> -- 
>>>
>>> *Rafael Benevides | Senior Software Engineer*
>>> JBoss Developer
>>> M: +55-61-9269-6576
>>>
>>> Red Hat
>>>
>>> Better technology. Faster innovation. Powered by community
>>> collaboration.
>>> See how it works at www.redhat.com <http://www.redhat.com/>
>>>
>>> LinkedIn <http://www.linkedin.com/company/3258288> Youtube
>>> <https://www.youtube.com/redhatlatam>
>>>
>>>
>>> _______________________________________________
>>> jbossdeveloper mailing list
>>> jbossdeveloper at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>
>>
>> -- 
>> Marek Novotny
>> --
>> WFK and Seam Product Lead
>>
>> Red Hat Czech s.r.o.
>> Purkynova 99
>> 612 45 Brno
>>
>>
>> _______________________________________________
>> jbossdeveloper mailing list
>> jbossdeveloper at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>


-- 
Marek Novotny
--
WFK and Seam Product Lead

Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150127/2c12296b/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 4815 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150127/2c12296b/attachment-0001.jpe 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 597 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150127/2c12296b/attachment-0002.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 616 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbossdeveloper/attachments/20150127/2c12296b/attachment-0003.png 

From max.andersen at redhat.com  Wed Jan 28 08:16:08 2015
From: max.andersen at redhat.com (Max Rydahl Andersen)
Date: Wed, 28 Jan 2015 14:16:08 +0100
Subject: [jbossdeveloper] JBoss Developer Materials Owners
In-Reply-To: <54C2953B.2070806@redhat.com>
References: <54C2953B.2070806@redhat.com>
Message-ID: <5D1872CA-3A6A-4083-B194-A45715181091@redhat.com>

Awesome to have this gathered on one page. Very helpful (if I can 
remember to find it again ;)

thanks,
Max

> Hi all,
>
> As JBoss Developer Materials keeps growing, sometimes it can be a hard 
> task when it's needed to deal with many products and components.
>
> To make easy to identify the person that should be contacted in case 
> of any issues, the following MOJO Document: 
> https://mojo.redhat.com/docs/DOC-1010716 have been created to make it 
> ease to contact the right person in case of issues.
>
> Please, take a look at the document and feel free to edit it in case 
> you want to add/replace the person that should be contact. We also 
> encourage Quickstarts/BOMs/Archetypes owners to join 
> https://lists.jboss.org/mailman/listinfo/jbossdeveloper to keep them 
> aware of latests discussion, news and guildeline updates.
>
> Thanks so much!
>
> -- 
>
> *Rafael Benevides | Senior Software Engineer*
> JBoss Developer
> M: +55-61-9269-6576
>
> Red Hat
>
> Better technology. Faster innovation. Powered by community 
> collaboration.
> See how it works at www.redhat.com <http://www.redhat.com/>
>
> LinkedIn <http://www.linkedin.com/company/3258288> Youtube 
> <https://www.youtube.com/redhatlatam>


/max
http://about.me/maxandersen