+1 to the proposal and +1 to ask help from a committer if the Project Lead is not available. Also, when asking for a committer's help to promote a release you just did on a contrib project, theoretically that committer should also check if you are the project's lead and if proper jira versions have been created. We could document this on contrib.xwiki.org as part of the content of an email template to use for such promotion requests. Something like: "Hi, I`m the Project Lead for project X and I have just released version Y. Here is the Jira link to the issues fixed in this version and here is the Jira link for the new iteration's version." (or along those lines). Thanks, Eduard On Wed, Jul 15, 2015 at 3:01 PM, [email protected] <[email protected]> wrote:

No other opinions?

Thanks -Vincent

On 9 Jul 2015 at 11:48:27, Ecaterina Moraru (Valica) ([email protected]) wrote:

+1

Additionally, if the Project Lead is unavailable, the release could still be performed with the help of a committer, after the release intent has been announced on the mailinglists.

Thanks, Caty

On Thu, Jul 9, 2015 at 12:11 PM, [email protected] <[email protected]> wrote:

...

Hi devs,

I’d like to propose to add some guidelines to contrib.xwiki.org when someone wants to release a project, especially when that person is not the project lead.

* The person wanting to do the release should contact the project lead, preferable either through IRC or the mailing list to mention its intent to perform a new release. ** This allows anyone who also want to have some issue fixed be able to do so in the same release for example. ** Usually that person will not have the permission to create a version in JIRA for that project and thus he/she’ll need the Project Lead’s help for that

WDYT?

Thanks -Vincent

_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

On 11 Feb 2016 at 12:02:45, [email protected] ([email protected](mailto:[email protected])) wrote:

Hi devs,

I’d like to conclude this discussion (so far only Edy, Caty and myself have expressed an opinion and we need more opinions).

I’d also like to modify it a bit, as follows:

I’d like to propose to add some guidelines to contrib.xwiki.org when a committer of xwiki-contrib wants to release an extension:

* Always send a Proposal mail to the devs list, announcing the wish to perform a release, with the following information: ** A jira link to the fixed issues that will be in that release ** The version id that will be released * Wait for at least 24 hours to let others the time to review some commits, test the extension, verify the list of issues, provides comments, etc. This is also important so that the project lead can talk to the committer wishing to perform the release if he wants to (to sync on stuff planned, etc). * Before the release is done, release the version in JIRA and create the next version (so that future work can be planned). If the committer doesn’t have access, ask for help on IRC or in the mail proposal mail.

* Before the release is done, integrate translations from l10n (if any). Thanks -Vincent

* Once the release is performed, update the documentation on xwiki.org(http://xwiki.org) (including the release notes section) * Send an [ANN] mail on the users list to announce the release, with a link to the page on e.x.o and to the Release Notes on e.x.o

Some notes: * This process is really lightweight and for example much simpler than the one at the ASF (they require a vote, waiting for longer, etc). * I don’t feel we can reduce the wait time to less than 24 hours. It’s already very very short for the community to be able to react (not everyone is working on xwiki full time!). * Compared from the previous proposal this allows any committer to perform a release and not have to wait on the lead to be available, while at the same time allowing some time for the lead to react if need be (although I agree that 24 hours is quite short. However in case of mistakes it should be easy to re-release a new version quickly too). * The idea of this revised proposal is to try to make extensions releases more fluid.

WDYT?

Thanks -Vincent

On 9 Jul 2015 at 11:11:57, [email protected] ([email protected](mailto:[email protected])) wrote:

...

Hi devs,

I’d like to propose to add some guidelines to contrib.xwiki.org when someone wants to release a project, especially when that person is not the project lead.

* The person wanting to do the release should contact the project lead, preferable either through IRC or the mailing list to mention its intent to perform a new release. ** This allows anyone who also want to have some issue fixed be able to do so in the same release for example. ** Usually that person will not have the permission to create a version in JIRA for that project and thus he/she’ll need the Project Lead’s help for that

WDYT?

Thanks -Vincent

_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

On 11 Feb 2016 at 16:45:02, Ecaterina Moraru (Valica) ([email protected](mailto:[email protected])) wrote:

Some notes:

- if the developer already did PRs somehow other committers were notified about changed in the app. I don't see how the 24 h would help somehow, since reviewing should be done based on issues and not releases;

Because a release is an important step. It’s about making the work of developers available to the outside world as a runtime. The quality of it is crucial and it affects the overall perceived quality of the XWiki project overall. You shouldn’t release lightly and this requires oversight and agreements from the persons involved with the extension. Also don’t forget that the purpose of contrib is to develop xwiki extensions collaboratively. A developer doing cowboy development on his own without letting anyone know about it is not a healthy practice. Said differently, we don’t ask for roadmap for extensions but the very least is to announce the wish to do a release IMO. Note: In various projects I know the rule is much harsher than this and it requires a proper VOTE with 7Z hours of waiting.

- there are many apps on e.x.o (around 800).

This is not fully correct. I’d say there are about a hundred. The rest are snippets or core extensions.

Sending [ANN] for XE is doable since they are big releases and usually take around 3 months of development. But having ANN mails for every bugfix release on contrib app IMO is an overkill.

This is what is happening in lots of communities I know (Maven and others). I’m not sure why it’s bad to let users know about a new version of an Extension. Now I agree that it doesn’t have to be by mail, see below. Some ideas: - If you release an extension very fast over a week you could group the release announcements into a single one maybe.  - Maybe releasing every time there’s a single issue closed for it is also a bit overkill and the RM should wait a bit more between releases. - Another idea would be to not send mail announcements but instead have a news.xwiki.org wiki that would list all releases (along with a RSS feed for those who’d want to be notified) + announcing releases on twitter using the xwikiorg account. Thoughts? Thanks -Vincent PS: BTW do you agree about the rest, you didn’t say anything about it?

Thanks, Caty

On Thu, Feb 11, 2016 at 1:51 PM, [email protected] wrote:

...

On 11 Feb 2016 at 12:02:45, [email protected] ([email protected](mailto: [email protected])) wrote:

...

Hi devs,

I’d like to conclude this discussion (so far only Edy, Caty and myself have expressed an opinion and we need more opinions).

I’d also like to modify it a bit, as follows:

I’d like to propose to add some guidelines to contrib.xwiki.org when a committer of xwiki-contrib wants to release an extension:

* Always send a Proposal mail to the devs list, announcing the wish to perform a release, with the following information: ** A jira link to the fixed issues that will be in that release ** The version id that will be released * Wait for at least 24 hours to let others the time to review some commits, test the extension, verify the list of issues, provides comments, etc. This is also important so that the project lead can talk to the committer wishing to perform the release if he wants to (to sync on stuff planned, etc). * Before the release is done, release the version in JIRA and create the next version (so that future work can be planned). If the committer doesn’t have access, ask for help on IRC or in the mail proposal mail.

* Before the release is done, integrate translations from l10n (if any).

Thanks -Vincent

...

* Once the release is performed, update the documentation on xwiki.org( http://xwiki.org) (including the release notes section) * Send an [ANN] mail on the users list to announce the release, with a link to the page on e.x.o and to the Release Notes on e.x.o

Some notes: * This process is really lightweight and for example much simpler than the one at the ASF (they require a vote, waiting for longer, etc). * I don’t feel we can reduce the wait time to less than 24 hours. It’s already very very short for the community to be able to react (not everyone is working on xwiki full time!). * Compared from the previous proposal this allows any committer to perform a release and not have to wait on the lead to be available, while at the same time allowing some time for the lead to react if need be (although I agree that 24 hours is quite short. However in case of mistakes it should be easy to re-release a new version quickly too). * The idea of this revised proposal is to try to make extensions releases more fluid.

WDYT?

Thanks -Vincent

On 9 Jul 2015 at 11:11:57, [email protected] ([email protected] (mailto:[email protected])) wrote:

...

Hi devs,

I’d like to propose to add some guidelines to contrib.xwiki.org when someone wants to release a project, especially when that person is not the project lead.

* The person wanting to do the release should contact the project lead, preferable either through IRC or the mailing list to mention its intent to perform a new release. ** This allows anyone who also want to have some issue fixed be able to do so in the same release for example. ** Usually that person will not have the permission to create a version in JIRA for that project and thus he/she’ll need the Project Lead’s help for that

WDYT?

Thanks -Vincent

On 11 Feb 2016 at 18:32:04, Eduard Moraru ([email protected](mailto:[email protected])) wrote:

On Thu, Feb 11, 2016 at 6:26 PM, [email protected] wrote:

...

On 11 Feb 2016 at 16:45:02, Ecaterina Moraru (Valica) ([email protected] (mailto:[email protected])) wrote:

...

Some notes:

- if the developer already did PRs somehow other committers were notified about changed in the app. I don't see how the 24 h would help somehow, since reviewing should be done based on issues and not releases;

Because a release is an important step. It’s about making the work of developers available to the outside world as a runtime. The quality of it is crucial and it affects the overall perceived quality of the XWiki project overall.

You shouldn’t release lightly and this requires oversight and agreements from the persons involved with the extension.

Also don’t forget that the purpose of contrib is to develop xwiki extensions collaboratively. A developer doing cowboy development on his own without letting anyone know about it is not a healthy practice.

Said differently, we don’t ask for roadmap for extensions but the very least is to announce the wish to do a release IMO.

Note: In various projects I know the rule is much harsher than this and it requires a proper VOTE with 7Z hours of waiting.

...

- there are many apps on e.x.o (around 800).

This is not fully correct. I’d say there are about a hundred. The rest are snippets or core extensions.

...

Sending [ANN] for XE is doable since they are big releases and usually take around 3 months of development. But having ANN mails for every bugfix release on contrib app IMO is an overkill.

This is what is happening in lots of communities I know (Maven and others). I’m not sure why it’s bad to let users know about a new version of an Extension. Now I agree that it doesn’t have to be by mail, see below.

Some ideas: - If you release an extension very fast over a week you could group the release announcements into a single one maybe. - Maybe releasing every time there’s a single issue closed for it is also a bit overkill and the RM should wait a bit more between releases. - Another idea would be to not send mail announcements but instead have a news.xwiki.org wiki that would list all releases (along with a RSS feed for those who’d want to be notified) + announcing releases on twitter using the xwikiorg account.

http://www.xwiki.org/xwiki/bin/view/Blog/ ? (Maybe with some "Contrib" and "Release" categories)

Indeed, good idea, don’t know why I didn’t think about it :) Thanks -Vincent

...

Thoughts?

Thanks -Vincent

PS: BTW do you agree about the rest, you didn’t say anything about it?

...

Thanks, Caty

On Thu, Feb 11, 2016 at 1:51 PM, [email protected] wrote:

...

On 11 Feb 2016 at 12:02:45, [email protected] ([email protected]

(mailto:

...

[email protected])) wrote:

...

Hi devs,

I’d like to conclude this discussion (so far only Edy, Caty and myself have expressed an opinion and we need more opinions).

I’d also like to modify it a bit, as follows:

I’d like to propose to add some guidelines to contrib.xwiki.org when a committer of xwiki-contrib wants to release an extension:

* Always send a Proposal mail to the devs list, announcing the wish to perform a release, with the following information: ** A jira link to the fixed issues that will be in that release ** The version id that will be released * Wait for at least 24 hours to let others the time to review some commits, test the extension, verify the list of issues, provides comments, etc. This is also important so that the project lead can talk to the committer wishing to perform the release if he wants to (to sync on stuff planned, etc). * Before the release is done, release the version in JIRA and create the next version (so that future work can be planned). If the committer doesn’t have access, ask for help on IRC or in the mail proposal mail.

* Before the release is done, integrate translations from l10n (if any).

Thanks -Vincent

...

* Once the release is performed, update the documentation on xwiki.org( http://xwiki.org) (including the release notes section) * Send an [ANN] mail on the users list to announce the release, with a link to the page on e.x.o and to the Release Notes on e.x.o

Some notes: * This process is really lightweight and for example much simpler than the one at the ASF (they require a vote, waiting for longer, etc). * I don’t feel we can reduce the wait time to less than 24 hours. It’s already very very short for the community to be able to react (not everyone is working on xwiki full time!). * Compared from the previous proposal this allows any committer to perform a release and not have to wait on the lead to be available, while at the same time allowing some time for the lead to react if need be (although I agree that 24 hours is quite short. However in case of mistakes it should be easy to re-release a new version quickly too). * The idea of this revised proposal is to try to make extensions releases more fluid.

WDYT?

Thanks -Vincent

On 9 Jul 2015 at 11:11:57, [email protected] ([email protected] (mailto:[email protected])) wrote:

...

Hi devs,

I’d like to propose to add some guidelines to contrib.xwiki.org when someone wants to release a project, especially when that person is not the project lead.

* The person wanting to do the release should contact the project lead, preferable either through IRC or the mailing list to mention its intent to perform a new release. ** This allows anyone who also want to have some issue fixed be able to do so in the same release for example. ** Usually that person will not have the permission to create a version in JIRA for that project and thus he/she’ll need the Project Lead’s help for that

WDYT?

Thanks -Vincent

On 1 Mar 2016 at 17:35:54, Marius Dumitru Florea ([email protected](mailto:[email protected])) wrote:

On Thu, Feb 11, 2016 at 1:02 PM, [email protected] wrote:

...

Hi devs,

I’d like to conclude this discussion (so far only Edy, Caty and myself have expressed an opinion and we need more opinions).

I’d also like to modify it a bit, as follows:

I’d like to propose to add some guidelines to contrib.xwiki.org when a committer of xwiki-contrib wants to release an extension:

* Always send a Proposal mail to the devs list, announcing the wish to perform a release, with the following information: ** A jira link to the fixed issues that will be in that release ** The version id that will be released

...

* Wait for at least 24 hours to let others the time to review some commits, test the extension, verify the list of issues, provides comments, etc. This is also important so that the project lead can talk to the committer wishing to perform the release if he wants to (to sync on stuff planned, etc).

As a project lead I would like to be able to release ASAP whenever there's a need for a new version (e.g. a critical bug fix), without waiting 24h. The project lead should know pretty well who's working actively on the project and can ping them directly using faster communication channels, like IRC.

For XWiki we wait 72 hours (and we’re supposed to send VOTE emails for releases) so 24 hours is an improvement. The goal of contrib is to work with others, i.e. it’s no longer someone’s projet anymore (I’ve been thinking a lot about this and I'm going to send a new proposal to remove the concept of lead soon), so releasing without letting any know or the time to comment is not very nice (even if you’re currently alone on the project, since the goal is to have other participants). Thanks -Vincent

...

* Before the release is done, release the version in JIRA and create the next version (so that future work can be planned). If the committer doesn’t have access, ask for help on IRC or in the mail proposal mail. * Once the release is performed, update the documentation on xwiki.org (including the release notes section)

* Send an [ANN] mail on the users list to announce the release, with a link

...

to the page on e.x.o and to the Release Notes on e.x.o

Some notes: * This process is really lightweight and for example much simpler than the one at the ASF (they require a vote, waiting for longer, etc). * I don’t feel we can reduce the wait time to less than 24 hours. It’s already very very short for the community to be able to react (not everyone is working on xwiki full time!). * Compared from the previous proposal this allows any committer to perform a release and not have to wait on the lead to be available, while at the same time allowing some time for the lead to react if need be (although I agree that 24 hours is quite short. However in case of mistakes it should be easy to re-release a new version quickly too). * The idea of this revised proposal is to try to make extensions releases more fluid.

WDYT?

Thanks -Vincent

On 9 Jul 2015 at 11:11:57, [email protected] ([email protected](mailto: [email protected])) wrote:

...

Hi devs,

I’d like to propose to add some guidelines to contrib.xwiki.org when someone wants to release a project, especially when that person is not the project lead.

* The person wanting to do the release should contact the project lead, preferable either through IRC or the mailing list to mention its intent to perform a new release. ** This allows anyone who also want to have some issue fixed be able to do so in the same release for example. ** Usually that person will not have the permission to create a version in JIRA for that project and thus he/she’ll need the Project Lead’s help for that

WDYT?

Thanks -Vincent