HttpService progress (help)...

[Sten Roger Sandvik <sr...@x3m.com>]

Hi.

I have now done the first step by importing the new httpservice
implementation into svn. The logical step further is to work towards a 2.0.0
release. This involves fixing some known bugs and releasing some
intermediate snapshot versions so people can try it out. Have some questions
regarding the process:

1) Can I assign issues to a version in JIRA? Can anyone create a version
label "http-2.0.0" or someting? Is this the way you guys do it?
2) Who drives the release of individual components? I can drive the "http"
dev-release process if that suites everybody.
3) Any rules regarding when to do a release or snapshot releases of
individual components?

Would really like release a 2.0.0 version as soon as possible. Have some
issues that I want to resolve (will put it into JIRA in the next days), but
the sooner the release the better. For me atleast :-)

Regards,
Sten Roger

Re: HttpService progress (help)...

[Felix Meschberger <fm...@gmail.com>]

Hi Sten,

Sorry for the delay ...

Sten Roger Sandvik schrieb:
> Great. I do not want to release individual bundles under http. Always the
> same version number (atleast for now).

Fine.

> Another question: What about
> documentation? 

Yes, please ;-)

> Would really like to include a Confluence entry on how to use
> the new http bundles. Any structures I should follow?

Except that we document below "subprojects" there is to my knowledge no
written prescription....

You need a Confluence account to be able to edit documents (you can
create one yourself). Please tell me your confluence account ID so that
I can enable your account for editing our site.


Regards
Felix


> 
> On Wed, Sep 16, 2009 at 8:42 AM, Felix Meschberger <fm...@gmail.com>wrote:
> 
>> Hi Sten,
>>
>> My €.02 below...
>>
>> Sten Roger Sandvik schrieb:
>>> I have now done the first step by importing the new httpservice
>>> implementation into svn. The logical step further is to work towards a
>> 2.0.0
>>> release. This involves fixing some known bugs and releasing some
>>> intermediate snapshot versions so people can try it out. Have some
>> questions
>>> regarding the process:
>>>
>>> 1) Can I assign issues to a version in JIRA? Can anyone create a version
>>> label "http-2.0.0" or someting? Is this the way you guys do it?
>> I don't know whether you have permission to do so (so I just created
>> it). I also added you to the felix-committers group which gives you
>> committers permission on the JIRA FELIX project.
>>
>> Are you planning on releasing single http modules or always everything
>> together ? My personal opinion would be to have an initial http-2.0.0
>> release encompassing "everything" and then release modules as required.
>>
>> WDYT ?
>>
>>> 2) Who drives the release of individual components? I can drive the
>> "http"
>>> dev-release process if that suites everybody.
>> According to [1] every committer can be a release manager, which is the
>> person driving the release. So if you think a release is due, you might
>> want to post a quick poll on the list and then just do it.
>>
>> You do this by following the release management guide at [2].
>>
>>> 3) Any rules regarding when to do a release or snapshot releases of
>>> individual components?
>> None that I would know of. Snapshot releases are done as required with
>> no formal processes. But keep in mind SNAPSHOT "releases" are not
>> releases in the understanding of Apache.
>>
>> Whether you release all http parts together or indivually is up to you
>> as the release manager. As said above, I propose to do an initial "full
>> release" and later release modules as required.
>>
>>
>>> Would really like release a 2.0.0 version as soon as possible. Have some
>>> issues that I want to resolve (will put it into JIRA in the next days),
>> but
>>> the sooner the release the better. For me atleast :-)
>> Having a first release soon, would definitely be a good thing.
>>
>> Regards
>> Felix
>>
>>
>> [1]
>> http://incubator.apache.org/guides/releasemanagement.html#glossary-release-manager
>> [2]http://felix.apache.org/site/release-management-nexus.html
>>
>>
> 

Re: HttpService progress (help)...

[Sten Roger Sandvik <sr...@x3m.com>]

Great. I do not want to release individual bundles under http. Always the
same version number (atleast for now). Another question: What about
documentation? Would really like to include a Confluence entry on how to use
the new http bundles. Any structures I should follow?

On Wed, Sep 16, 2009 at 8:42 AM, Felix Meschberger <fm...@gmail.com>wrote:

> Hi Sten,
>
> My €.02 below...
>
> Sten Roger Sandvik schrieb:
> > I have now done the first step by importing the new httpservice
> > implementation into svn. The logical step further is to work towards a
> 2.0.0
> > release. This involves fixing some known bugs and releasing some
> > intermediate snapshot versions so people can try it out. Have some
> questions
> > regarding the process:
> >
> > 1) Can I assign issues to a version in JIRA? Can anyone create a version
> > label "http-2.0.0" or someting? Is this the way you guys do it?
>
> I don't know whether you have permission to do so (so I just created
> it). I also added you to the felix-committers group which gives you
> committers permission on the JIRA FELIX project.
>
> Are you planning on releasing single http modules or always everything
> together ? My personal opinion would be to have an initial http-2.0.0
> release encompassing "everything" and then release modules as required.
>
> WDYT ?
>
> > 2) Who drives the release of individual components? I can drive the
> "http"
> > dev-release process if that suites everybody.
>
> According to [1] every committer can be a release manager, which is the
> person driving the release. So if you think a release is due, you might
> want to post a quick poll on the list and then just do it.
>
> You do this by following the release management guide at [2].
>
> > 3) Any rules regarding when to do a release or snapshot releases of
> > individual components?
>
> None that I would know of. Snapshot releases are done as required with
> no formal processes. But keep in mind SNAPSHOT "releases" are not
> releases in the understanding of Apache.
>
> Whether you release all http parts together or indivually is up to you
> as the release manager. As said above, I propose to do an initial "full
> release" and later release modules as required.
>
>
> > Would really like release a 2.0.0 version as soon as possible. Have some
> > issues that I want to resolve (will put it into JIRA in the next days),
> but
> > the sooner the release the better. For me atleast :-)
>
> Having a first release soon, would definitely be a good thing.
>
> Regards
> Felix
>
>
> [1]
> http://incubator.apache.org/guides/releasemanagement.html#glossary-release-manager
> [2]http://felix.apache.org/site/release-management-nexus.html
>
>

Re: HttpService progress (help)...

[Felix Meschberger <fm...@gmail.com>]

Hi Sten,

My €.02 below...

Sten Roger Sandvik schrieb:
> I have now done the first step by importing the new httpservice
> implementation into svn. The logical step further is to work towards a 2.0.0
> release. This involves fixing some known bugs and releasing some
> intermediate snapshot versions so people can try it out. Have some questions
> regarding the process:
> 
> 1) Can I assign issues to a version in JIRA? Can anyone create a version
> label "http-2.0.0" or someting? Is this the way you guys do it?

I don't know whether you have permission to do so (so I just created
it). I also added you to the felix-committers group which gives you
committers permission on the JIRA FELIX project.

Are you planning on releasing single http modules or always everything
together ? My personal opinion would be to have an initial http-2.0.0
release encompassing "everything" and then release modules as required.

WDYT ?

> 2) Who drives the release of individual components? I can drive the "http"
> dev-release process if that suites everybody.

According to [1] every committer can be a release manager, which is the
person driving the release. So if you think a release is due, you might
want to post a quick poll on the list and then just do it.

You do this by following the release management guide at [2].

> 3) Any rules regarding when to do a release or snapshot releases of
> individual components?

None that I would know of. Snapshot releases are done as required with
no formal processes. But keep in mind SNAPSHOT "releases" are not
releases in the understanding of Apache.

Whether you release all http parts together or indivually is up to you
as the release manager. As said above, I propose to do an initial "full
release" and later release modules as required.


> Would really like release a 2.0.0 version as soon as possible. Have some
> issues that I want to resolve (will put it into JIRA in the next days), but
> the sooner the release the better. For me atleast :-)

Having a first release soon, would definitely be a good thing.

Regards
Felix


[1]http://incubator.apache.org/guides/releasemanagement.html#glossary-release-manager
[2]http://felix.apache.org/site/release-management-nexus.html