Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jwt-dev] New Bugzilla component "Releng"

Hi Florian,

Thanks for this new component!
I'll move all build related bugs from Yearly Release to Releng now.

Regards
Mickael


Florian Lautenbacher a écrit :
Hi together,

as we discussed recently I now created a new Bugzilla component called
"Releng" with default email adress jwt.releng-inbox@xxxxxxxxxxx. If you are
interested in receiving messages about the current build process, please add
this email adress to the watch list in your bugzilla preferences.

Best regards,

Florian
-----Ursprüngliche Nachricht-----
Von: jwt-dev-bounces@xxxxxxxxxxx [mailto:jwt-dev-bounces@xxxxxxxxxxx] Im
Auftrag von Mickael Istria
Gesendet: 24 February 2009 14:26
An: Java Workflow Toolbox
Betreff: Re: AW: [jwt-dev] Separate Bugzilla "Yearly Release" component
into2 components: Releng and "Yearly release"

Hello Florian,

I agree that the Releng related bugs should be linked to another address,
such as jwt.releng-inbox@xxxxxxxxxxx.
And "Yearly Release" bugs should be put on the right component (releng or
we) according to their content (build/test/p2... or code requirements).

Then it seems like we are OK on this topic!

Regards,
Mickael

Florian Lautenbacher a écrit :
Hi Mickael,

I would agree to the new Bugzilla component. Right now the yearly release bugs are all send to jwt.we-inbox@eclipse, because I didn't ask for an own mailing address for this one. Shall we now asks for an own email address for jwt.releng-inbox@eclipse? Otherwise people only interested in the workflow editor will get messed up with a lot of emails they are not at all interested in...

Best regards and "hellau", "alaaf", "wehri-wehro" or simply "Happy carnival",

Florian


-----Ursprüngliche Nachricht-----
Von: jwt-dev-bounces@xxxxxxxxxxx [mailto:jwt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Mickael Istria
Gesendet: 24 February 2009 09:50
An: Java Workflow Toolbox
Betreff: [jwt-dev] Separate Bugzilla "Yearly Release" component into 2
components: Releng and "Yearly release"

Hi all,

When taking a look at the current bugs in the Yearly Release components, we can see that there are 2 kinds of bugs, that do not share
the same goal:
* What I'd call the "releng" bugs, that are about issues or improvements about our build process (technically speaking) * "Yearly Release" bugs, that are external requirements to join the Eclipse release train.

Since their aims are different, I suggest that we create a new component
("releng") where we can place all build/update-site related issues.

What do you think of that?

Regards,
Mickael
_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev

_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev

_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev

_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev



Back to the top