[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cross-project-issues-dev] Joint N&N page for the release train
|
On 2 Feb 2015, at 18:19, Doug Schaefer wrote:
From: Lars Vogel
<lars.vogel@xxxxxxxxxxx<mailto:lars.vogel@xxxxxxxxxxx>>
Ideally, we have a product/project manager who puts all this
together. Don’t let engineers do your marketing :).
-1, having worked for a large software company in the past, I think
the current platform approach of having the developer describe his
development is much more efficient.
Efficient, yes. But effective at producing content that
users/customers may be interested in and help sell them on your
product without getting lost in the tragedy of the commons? To be
honest, I think a N&N for the entire release train that isn’t
managed by a single person will be a disaster.
having some review and proof read the content is always good - but to
get to that point we need the content produced first. And for that the
one who actually made the content is best.
I can say that is what we do on jboss tools side and added in a bit of
automation to turn this:
https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew
into this:
http://tools.jboss.org/documentation/whatsnew/jbosstools/4.2.0.Final.html
Each dev makes an asciidoc in each of their components dir with a
component version + link to "release train" its included in and we
aggregate it.
Then nearing major release we go through and clean up if we feel its
necessary.
/max
On Mon, Feb 2, 2015 at 6:04 PM, Doug Schaefer
<dschaefer@xxxxxxx<mailto:dschaefer@xxxxxxx>> wrote:
Ideally, we have a product/project manager who puts all this together.
Don’t let engineers do your marketing :).
D
From: Wayne Beaton <wayne@xxxxxxxxxxx<mailto:wayne@xxxxxxxxxxx>>
Organization: The Eclipse Foundation
Reply-To: Cross project issues
<cross-project-issues-dev@xxxxxxxxxxx<mailto:cross-project-issues-dev@xxxxxxxxxxx>>
Date: Monday, February 2, 2015 at 10:53 AM
To:
"cross-project-issues-dev@xxxxxxxxxxx<mailto:cross-project-issues-dev@xxxxxxxxxxx>"
<cross-project-issues-dev@xxxxxxxxxxx<mailto:cross-project-issues-dev@xxxxxxxxxxx>>
Subject: Re: [cross-project-issues-dev] Joint N&N page for the release
train
Okay. Avoidance of more work is a requirement. Forget all that
silliness about a common XML file format and putting extra files in
features.
Wayne
On 02/02/15 10:03 AM, Daniel Megert wrote:
For us it would mean more work, which I'd like to avoid. Having one
document easily allows to tools to e.g. check for XHTML validity, and
help fix such issues. If the document is generated out of pieces, then
it can be a tedious task to get to a generated document that is valid.
The extension point doc is such an example: the text for the elements
is entered in the extension point editor in separate fields, and
during build a document is generated. If there are errors, it's hard
to detect and fix them. Also, spell checking a single document is
easier than doing the same over different fragments.
Another point is, that the N&N of a release is not simply the
collection of the milestone N&Ns. We e.g. put the new Quick Fixes
under one item for the release, or a feature that got developed over
several milestones with entries in the corresponding milestone N&Ns
will have to be collapsed into a single entry.
I'd like to keep our approach for our project, since it works well for
us, and produces good quality N&N documents. If other projects want to
try out something new where the N&N is generated, and provide feedback
about how it worked for them, that's of course fine for me too.
Dani
--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
[EclipseCon 2015]<http://www.eclipsecon.org/na2015>
---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client or other applicable privileges), or constitute
non-public information. Any use of this information by anyone other
than the intended recipient is prohibited. If you have received this
transmission in error, please immediately reply to the sender and
delete this information from your system. Use, dissemination,
distribution, or reproduction of this transmission by unintended
recipients is not authorized and may be unlawful.
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx<mailto:cross-project-issues-dev@xxxxxxxxxxx>
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Geschäftsführer
vogella GmbH
Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (032) 221739404, Email:
lars.vogel@xxxxxxxxxxx<mailto:lars.vogel@xxxxxxxxxxx>, Web:
http://www.vogella.com
---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client or other applicable privileges), or constitute
non-public information. Any use of this information by anyone other
than the intended recipient is prohibited. If you have received this
transmission in error, please immediately reply to the sender and
delete this information from your system. Use, dissemination,
distribution, or reproduction of this transmission by unintended
recipients is not authorized and may be unlawful.
[728X90.jpg]
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
/max
http://about.me/maxandersen