You are viewing a plain text version of this content. The canonical link for it is here.
Posted to stonehenge-dev@incubator.apache.org by Selvaratnam Uthaiyashankar <ut...@gmail.com> on 2009/04/23 05:10:29 UTC
Finalizing Release artifacts for M1
Hi,
We have to finalize what are the release artifacts we are going to release.
I can think of two options.
Option 1
-------------
stonehenge-stocktrader-m1-incubating-src
|
|- dotnet src
|
|- php src
|
|- wsas src
stonehenge-stocktrader-m1-incubating
|
|- dotnet bin
|
|- php (same as src, packed in both places)
|
|- wsas bin
Here we have only two artifacts, but if somebody needs to check only one of
the implementation, still they have to download all the other
implementations
as well.
Option 2
--------------
stonehenge-stocktrader-dotnet-m1-incubating
stonehenge-stocktrader-dotnet-m1-incubating-src
stonehenge-stocktrader-php-m1-incubating
stonehenge-stocktrader-wsas-m1-incubating
stonehenge-stocktrader-wsas-m1-incubating-src
Here, the number of artifacts are high. But users can download individual
implementations.
I prefer option 1. What others are thinking?
In addition to that, all the artifacts should contain following files:
* DISCLAIMER
* LICENSE
* NOTICE
* README
* Release-Note
NOTICE file will have only Apache Licence. Do we have to add any other
information?
Also, We can generate pdf from wiki page (installation guide) and include in
the release packages. Should any other files be added? Any comments?
Regards,
Shankar
--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"
RE: Finalizing Release artifacts for M1
Posted by Ben Dewey <Be...@26ny.com>.
My question was more for Linux users. I'm assuming windows users are fine with having .NET src/bins.
My vote is for option #1
________________________________________
From: Selvaratnam Uthaiyashankar [uthaiyashankar@gmail.com]
Sent: Friday, April 24, 2009 12:06 AM
To: stonehenge-dev@incubator.apache.org
Subject: Re: Finalizing Release artifacts for M1
Hi Ben,
For each src and binary artifact, we have to have a linux version and
windows version. src version can include .NET sources in both places. We
have to remove .NET binaries from linux binary dist. If your question is for
windows users, then yes, it is a problem. They have to download .NET as
well.
Regards,
Shankar
On Fri, Apr 24, 2009 at 9:19 AM, Ben Dewey <Be...@26ny.com> wrote:
> From an interopability standpoint I would vote for #1. My only thought is
> if you want the PHP/WSAS/MySQL to exist as a download seperate from .NET how
> would that be handled?
>
> ________________________________________
> From: Selvaratnam Uthaiyashankar [uthaiyashankar@gmail.com]
> Sent: Thursday, April 23, 2009 1:10 AM
> To: stonehenge-dev@incubator.apache.org
> Subject: Finalizing Release artifacts for M1
>
> Hi,
>
> We have to finalize what are the release artifacts we are going to release.
> I can think of two options.
>
> Option 1
> -------------
>
> stonehenge-stocktrader-m1-incubating-src
> |
> |- dotnet src
> |
> |- php src
> |
> |- wsas src
>
>
> stonehenge-stocktrader-m1-incubating
> |
> |- dotnet bin
> |
> |- php (same as src, packed in both places)
> |
> |- wsas bin
>
> Here we have only two artifacts, but if somebody needs to check only one of
> the implementation, still they have to download all the other
> implementations
>
> as well.
>
>
> Option 2
> --------------
> stonehenge-stocktrader-dotnet-m1-incubating
> stonehenge-stocktrader-dotnet-m1-incubating-src
> stonehenge-stocktrader-php-m1-incubating
> stonehenge-stocktrader-wsas-m1-incubating
> stonehenge-stocktrader-wsas-m1-incubating-src
>
> Here, the number of artifacts are high. But users can download individual
> implementations.
>
> I prefer option 1. What others are thinking?
>
>
> In addition to that, all the artifacts should contain following files:
> * DISCLAIMER
> * LICENSE
> * NOTICE
> * README
> * Release-Note
>
> NOTICE file will have only Apache Licence. Do we have to add any other
> information?
>
> Also, We can generate pdf from wiki page (installation guide) and include
> in
> the release packages. Should any other files be added? Any comments?
>
> Regards,
> Shankar
>
> --
> S.Uthaiyashankar
> Software Architect
> WSO2 Inc.
> http://wso2.com/ - "The Open Source SOA Company"
>
--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"
Re: Finalizing Release artifacts for M1
Posted by Selvaratnam Uthaiyashankar <ut...@gmail.com>.
Hi Ben,
For each src and binary artifact, we have to have a linux version and
windows version. src version can include .NET sources in both places. We
have to remove .NET binaries from linux binary dist. If your question is for
windows users, then yes, it is a problem. They have to download .NET as
well.
Regards,
Shankar
On Fri, Apr 24, 2009 at 9:19 AM, Ben Dewey <Be...@26ny.com> wrote:
> From an interopability standpoint I would vote for #1. My only thought is
> if you want the PHP/WSAS/MySQL to exist as a download seperate from .NET how
> would that be handled?
>
> ________________________________________
> From: Selvaratnam Uthaiyashankar [uthaiyashankar@gmail.com]
> Sent: Thursday, April 23, 2009 1:10 AM
> To: stonehenge-dev@incubator.apache.org
> Subject: Finalizing Release artifacts for M1
>
> Hi,
>
> We have to finalize what are the release artifacts we are going to release.
> I can think of two options.
>
> Option 1
> -------------
>
> stonehenge-stocktrader-m1-incubating-src
> |
> |- dotnet src
> |
> |- php src
> |
> |- wsas src
>
>
> stonehenge-stocktrader-m1-incubating
> |
> |- dotnet bin
> |
> |- php (same as src, packed in both places)
> |
> |- wsas bin
>
> Here we have only two artifacts, but if somebody needs to check only one of
> the implementation, still they have to download all the other
> implementations
>
> as well.
>
>
> Option 2
> --------------
> stonehenge-stocktrader-dotnet-m1-incubating
> stonehenge-stocktrader-dotnet-m1-incubating-src
> stonehenge-stocktrader-php-m1-incubating
> stonehenge-stocktrader-wsas-m1-incubating
> stonehenge-stocktrader-wsas-m1-incubating-src
>
> Here, the number of artifacts are high. But users can download individual
> implementations.
>
> I prefer option 1. What others are thinking?
>
>
> In addition to that, all the artifacts should contain following files:
> * DISCLAIMER
> * LICENSE
> * NOTICE
> * README
> * Release-Note
>
> NOTICE file will have only Apache Licence. Do we have to add any other
> information?
>
> Also, We can generate pdf from wiki page (installation guide) and include
> in
> the release packages. Should any other files be added? Any comments?
>
> Regards,
> Shankar
>
> --
> S.Uthaiyashankar
> Software Architect
> WSO2 Inc.
> http://wso2.com/ - "The Open Source SOA Company"
>
--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"
RE: Finalizing Release artifacts for M1
Posted by Ben Dewey <Be...@26ny.com>.
From an interopability standpoint I would vote for #1. My only thought is if you want the PHP/WSAS/MySQL to exist as a download seperate from .NET how would that be handled?
________________________________________
From: Selvaratnam Uthaiyashankar [uthaiyashankar@gmail.com]
Sent: Thursday, April 23, 2009 1:10 AM
To: stonehenge-dev@incubator.apache.org
Subject: Finalizing Release artifacts for M1
Hi,
We have to finalize what are the release artifacts we are going to release.
I can think of two options.
Option 1
-------------
stonehenge-stocktrader-m1-incubating-src
|
|- dotnet src
|
|- php src
|
|- wsas src
stonehenge-stocktrader-m1-incubating
|
|- dotnet bin
|
|- php (same as src, packed in both places)
|
|- wsas bin
Here we have only two artifacts, but if somebody needs to check only one of
the implementation, still they have to download all the other
implementations
as well.
Option 2
--------------
stonehenge-stocktrader-dotnet-m1-incubating
stonehenge-stocktrader-dotnet-m1-incubating-src
stonehenge-stocktrader-php-m1-incubating
stonehenge-stocktrader-wsas-m1-incubating
stonehenge-stocktrader-wsas-m1-incubating-src
Here, the number of artifacts are high. But users can download individual
implementations.
I prefer option 1. What others are thinking?
In addition to that, all the artifacts should contain following files:
* DISCLAIMER
* LICENSE
* NOTICE
* README
* Release-Note
NOTICE file will have only Apache Licence. Do we have to add any other
information?
Also, We can generate pdf from wiki page (installation guide) and include in
the release packages. Should any other files be added? Any comments?
Regards,
Shankar
--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"
Re: Finalizing Release artifacts for M1
Posted by Selvaratnam Uthaiyashankar <ut...@gmail.com>.
Hi,
I have added LICENSE, NOTICE, DISCLAIMER and README to
https://svn.apache.org/repos/asf/incubator/stonehenge/trunk/stocktrader
Please review and send the comments (Specially NOTICE, whether we have to
include any other copyright statements). We might have to improve README a
bit.
Regards,
Shankar
On Thu, Apr 23, 2009 at 10:40 AM, Selvaratnam Uthaiyashankar <
uthaiyashankar@gmail.com> wrote:
> Hi,
>
> We have to finalize what are the release artifacts we are going to release.
> I can think of two options.
>
> Option 1
> -------------
>
> stonehenge-stocktrader-m1-incubating-src
> |
> |- dotnet src
> |
> |- php src
> |
> |- wsas src
>
>
> stonehenge-stocktrader-m1-incubating
> |
> |- dotnet bin
> |
> |- php (same as src, packed in both places)
> |
> |- wsas bin
>
> Here we have only two artifacts, but if somebody needs to check only one of
> the implementation, still they have to download all the other
> implementations
>
> as well.
>
>
> Option 2
> --------------
> stonehenge-stocktrader-dotnet-m1-incubating
> stonehenge-stocktrader-dotnet-m1-incubating-src
> stonehenge-stocktrader-php-m1-incubating
> stonehenge-stocktrader-wsas-m1-incubating
> stonehenge-stocktrader-wsas-m1-incubating-src
>
> Here, the number of artifacts are high. But users can download individual
> implementations.
>
> I prefer option 1. What others are thinking?
>
>
> In addition to that, all the artifacts should contain following files:
> * DISCLAIMER
> * LICENSE
> * NOTICE
> * README
> * Release-Note
>
> NOTICE file will have only Apache Licence. Do we have to add any other
> information?
>
> Also, We can generate pdf from wiki page (installation guide) and include
> in the release packages. Should any other files be added? Any comments?
>
> Regards,
> Shankar
>
> --
> S.Uthaiyashankar
> Software Architect
> WSO2 Inc.
> http://wso2.com/ - "The Open Source SOA Company"
>
>
>
--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"
Re: Finalizing Release artifacts for M1
Posted by Chintana Wilamuna <ch...@gmail.com>.
On Thu, Apr 23, 2009 at 10:40 AM, Selvaratnam Uthaiyashankar
<ut...@gmail.com> wrote:
> I prefer option 1. What others are thinking?
I too prefer option 1, considering the objective of the project to
demonstrate interoperability between different platforms.
Bye,
-Chintana
--
http://engwar.com/
Re: Finalizing Release artifacts for M1
Posted by Selvaratnam Uthaiyashankar <ut...@gmail.com>.
hi Drew,
It will be in http://www.apache.org/dist/incubator/stonehenge (currently you
will get a 404). You can find more details about Incubator release procedure
in [1]
Regards,
Shankar
[1] http://incubator.apache.org/guides/releasemanagement.html
On Fri, Apr 24, 2009 at 9:16 AM, Drew Baird (Volt)
<a-...@microsoft.com>wrote:
> Hi Shankar,
> Where do the Release Artifacts live?
> Is there a tree in the repository?
> Thanks!
> Drew
>
>
> -----Original Message-----
> From: Selvaratnam Uthaiyashankar [mailto:uthaiyashankar@gmail.com]
> Sent: Thursday, April 23, 2009 8:23 PM
> To: stonehenge-dev@incubator.apache.org
> Subject: Re: Finalizing Release artifacts for M1
>
> Hi Scott,
>
> When we are releasing, all the artifacts will be archived (zip or tar.gz).
> So, in option 1, they can't download WSAS only. Thay can download the
> archive, unzip it and then get the WSAS.
>
> Regards,
> Shankar
>
> On Thu, Apr 23, 2009 at 9:38 PM, Scott Golightly <
> Scott_Golightly@hotmail.com> wrote:
>
> > I might be missing something but if someone really wanted to go to the
> > effort they could download just the WSAS or any other implementation from
> > option 1 while having the convenience of getting them all so I would vote
> > for option 1.
> >
> > Scott Golightly
> >
> > -----Original Message-----
> > From: Selvaratnam Uthaiyashankar [mailto:uthaiyashankar@gmail.com]
> > Sent: Wednesday, April 22, 2009 11:10 PM
> > To: stonehenge-dev@incubator.apache.org
> > Subject: Finalizing Release artifacts for M1
> >
> > Hi,
> >
> > We have to finalize what are the release artifacts we are going to
> release.
> > I can think of two options.
> >
> > Option 1
> > -------------
> >
> > stonehenge-stocktrader-m1-incubating-src
> > |
> > |- dotnet src
> > |
> > |- php src
> > |
> > |- wsas src
> >
> >
> > stonehenge-stocktrader-m1-incubating
> > |
> > |- dotnet bin
> > |
> > |- php (same as src, packed in both places)
> > |
> > |- wsas bin
> >
> > Here we have only two artifacts, but if somebody needs to check only one
> of
> > the implementation, still they have to download all the other
> > implementations
> >
> > as well.
> >
> >
> > Option 2
> > --------------
> > stonehenge-stocktrader-dotnet-m1-incubating
> > stonehenge-stocktrader-dotnet-m1-incubating-src
> > stonehenge-stocktrader-php-m1-incubating
> > stonehenge-stocktrader-wsas-m1-incubating
> > stonehenge-stocktrader-wsas-m1-incubating-src
> >
> > Here, the number of artifacts are high. But users can download individual
> > implementations.
> >
> > I prefer option 1. What others are thinking?
> >
> >
> > In addition to that, all the artifacts should contain following files:
> > * DISCLAIMER
> > * LICENSE
> > * NOTICE
> > * README
> > * Release-Note
> >
> > NOTICE file will have only Apache Licence. Do we have to add any other
> > information?
> >
> > Also, We can generate pdf from wiki page (installation guide) and include
> > in
> > the release packages. Should any other files be added? Any comments?
> >
> > Regards,
> > Shankar
> >
> > --
> > S.Uthaiyashankar
> > Software Architect
> > WSO2 Inc.
> > http://wso2.com/ - "The Open Source SOA Company"
> >
> >
>
>
> --
> S.Uthaiyashankar
> Software Architect
> WSO2 Inc.
> http://wso2.com/ - "The Open Source SOA Company"
>
--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"
RE: Finalizing Release artifacts for M1
Posted by "Drew Baird (Volt)" <a-...@microsoft.com>.
Hi Shankar,
Where do the Release Artifacts live?
Is there a tree in the repository?
Thanks!
Drew
-----Original Message-----
From: Selvaratnam Uthaiyashankar [mailto:uthaiyashankar@gmail.com]
Sent: Thursday, April 23, 2009 8:23 PM
To: stonehenge-dev@incubator.apache.org
Subject: Re: Finalizing Release artifacts for M1
Hi Scott,
When we are releasing, all the artifacts will be archived (zip or tar.gz).
So, in option 1, they can't download WSAS only. Thay can download the
archive, unzip it and then get the WSAS.
Regards,
Shankar
On Thu, Apr 23, 2009 at 9:38 PM, Scott Golightly <
Scott_Golightly@hotmail.com> wrote:
> I might be missing something but if someone really wanted to go to the
> effort they could download just the WSAS or any other implementation from
> option 1 while having the convenience of getting them all so I would vote
> for option 1.
>
> Scott Golightly
>
> -----Original Message-----
> From: Selvaratnam Uthaiyashankar [mailto:uthaiyashankar@gmail.com]
> Sent: Wednesday, April 22, 2009 11:10 PM
> To: stonehenge-dev@incubator.apache.org
> Subject: Finalizing Release artifacts for M1
>
> Hi,
>
> We have to finalize what are the release artifacts we are going to release.
> I can think of two options.
>
> Option 1
> -------------
>
> stonehenge-stocktrader-m1-incubating-src
> |
> |- dotnet src
> |
> |- php src
> |
> |- wsas src
>
>
> stonehenge-stocktrader-m1-incubating
> |
> |- dotnet bin
> |
> |- php (same as src, packed in both places)
> |
> |- wsas bin
>
> Here we have only two artifacts, but if somebody needs to check only one of
> the implementation, still they have to download all the other
> implementations
>
> as well.
>
>
> Option 2
> --------------
> stonehenge-stocktrader-dotnet-m1-incubating
> stonehenge-stocktrader-dotnet-m1-incubating-src
> stonehenge-stocktrader-php-m1-incubating
> stonehenge-stocktrader-wsas-m1-incubating
> stonehenge-stocktrader-wsas-m1-incubating-src
>
> Here, the number of artifacts are high. But users can download individual
> implementations.
>
> I prefer option 1. What others are thinking?
>
>
> In addition to that, all the artifacts should contain following files:
> * DISCLAIMER
> * LICENSE
> * NOTICE
> * README
> * Release-Note
>
> NOTICE file will have only Apache Licence. Do we have to add any other
> information?
>
> Also, We can generate pdf from wiki page (installation guide) and include
> in
> the release packages. Should any other files be added? Any comments?
>
> Regards,
> Shankar
>
> --
> S.Uthaiyashankar
> Software Architect
> WSO2 Inc.
> http://wso2.com/ - "The Open Source SOA Company"
>
>
--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"
Re: Finalizing Release artifacts for M1
Posted by Selvaratnam Uthaiyashankar <ut...@gmail.com>.
Hi Scott,
When we are releasing, all the artifacts will be archived (zip or tar.gz).
So, in option 1, they can't download WSAS only. Thay can download the
archive, unzip it and then get the WSAS.
Regards,
Shankar
On Thu, Apr 23, 2009 at 9:38 PM, Scott Golightly <
Scott_Golightly@hotmail.com> wrote:
> I might be missing something but if someone really wanted to go to the
> effort they could download just the WSAS or any other implementation from
> option 1 while having the convenience of getting them all so I would vote
> for option 1.
>
> Scott Golightly
>
> -----Original Message-----
> From: Selvaratnam Uthaiyashankar [mailto:uthaiyashankar@gmail.com]
> Sent: Wednesday, April 22, 2009 11:10 PM
> To: stonehenge-dev@incubator.apache.org
> Subject: Finalizing Release artifacts for M1
>
> Hi,
>
> We have to finalize what are the release artifacts we are going to release.
> I can think of two options.
>
> Option 1
> -------------
>
> stonehenge-stocktrader-m1-incubating-src
> |
> |- dotnet src
> |
> |- php src
> |
> |- wsas src
>
>
> stonehenge-stocktrader-m1-incubating
> |
> |- dotnet bin
> |
> |- php (same as src, packed in both places)
> |
> |- wsas bin
>
> Here we have only two artifacts, but if somebody needs to check only one of
> the implementation, still they have to download all the other
> implementations
>
> as well.
>
>
> Option 2
> --------------
> stonehenge-stocktrader-dotnet-m1-incubating
> stonehenge-stocktrader-dotnet-m1-incubating-src
> stonehenge-stocktrader-php-m1-incubating
> stonehenge-stocktrader-wsas-m1-incubating
> stonehenge-stocktrader-wsas-m1-incubating-src
>
> Here, the number of artifacts are high. But users can download individual
> implementations.
>
> I prefer option 1. What others are thinking?
>
>
> In addition to that, all the artifacts should contain following files:
> * DISCLAIMER
> * LICENSE
> * NOTICE
> * README
> * Release-Note
>
> NOTICE file will have only Apache Licence. Do we have to add any other
> information?
>
> Also, We can generate pdf from wiki page (installation guide) and include
> in
> the release packages. Should any other files be added? Any comments?
>
> Regards,
> Shankar
>
> --
> S.Uthaiyashankar
> Software Architect
> WSO2 Inc.
> http://wso2.com/ - "The Open Source SOA Company"
>
>
--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"
RE: Finalizing Release artifacts for M1
Posted by Scott Golightly <Sc...@hotmail.com>.
I might be missing something but if someone really wanted to go to the
effort they could download just the WSAS or any other implementation from
option 1 while having the convenience of getting them all so I would vote
for option 1.
Scott Golightly
-----Original Message-----
From: Selvaratnam Uthaiyashankar [mailto:uthaiyashankar@gmail.com]
Sent: Wednesday, April 22, 2009 11:10 PM
To: stonehenge-dev@incubator.apache.org
Subject: Finalizing Release artifacts for M1
Hi,
We have to finalize what are the release artifacts we are going to release.
I can think of two options.
Option 1
-------------
stonehenge-stocktrader-m1-incubating-src
|
|- dotnet src
|
|- php src
|
|- wsas src
stonehenge-stocktrader-m1-incubating
|
|- dotnet bin
|
|- php (same as src, packed in both places)
|
|- wsas bin
Here we have only two artifacts, but if somebody needs to check only one of
the implementation, still they have to download all the other
implementations
as well.
Option 2
--------------
stonehenge-stocktrader-dotnet-m1-incubating
stonehenge-stocktrader-dotnet-m1-incubating-src
stonehenge-stocktrader-php-m1-incubating
stonehenge-stocktrader-wsas-m1-incubating
stonehenge-stocktrader-wsas-m1-incubating-src
Here, the number of artifacts are high. But users can download individual
implementations.
I prefer option 1. What others are thinking?
In addition to that, all the artifacts should contain following files:
* DISCLAIMER
* LICENSE
* NOTICE
* README
* Release-Note
NOTICE file will have only Apache Licence. Do we have to add any other
information?
Also, We can generate pdf from wiki page (installation guide) and include in
the release packages. Should any other files be added? Any comments?
Regards,
Shankar
--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"