Re: [cross-project-issues-dev] Metadata for participating projects

2012-01-25 Thread Sven Efftinge
Hi all,

as you might know, we've recently restructured Xtext and moved the language 
Xtend to its own project under tools (tools.xtend).
I've just flipped the bits stating that Xtend is on the train and will update 
all the meta data as soon as the infrastructure is available and the move is 
completed.
Unfortunately we won't be able to contribute a build to M5 already but only for 
M6.

Best Regards,
Sven

On Jan 25, 2012, at 9:31 PM, Wayne Beaton wrote:

> Greetings.
> 
> Projects participating in the Juno simultaneous release are listed on the 
> "Releases" page [1]. There are currently 67 projects listed here. All 
> projects that are participating in Juno must have already flipped the 
> participation bit as described in the wiki [2]. If your project is missing 
> from this list, then you probably haven't flipped the bit; please contact the 
> planning council through your PMC immediately.
> 
> Please take a look at the releases page to make sure that the offset is 
> correct and that the project releases associated with your project have been 
> specified. Project releases specified in the project metadata that occur on 
> the day of the release are displayed here. Note that the name provided for 
> the release is normalized to a three part version number; release names that 
> do not contain numbers, or are labelled as a milestone (e.g. "1.0.0M2") are 
> ignored (i.e. it's not enough to label your release "Juno", but you could 
> label it "8.6 Juno").
> 
> Please also take a minute to ensure that the description for your project is 
> suitable. These are displayed on the Project Descriptions page [3] and may be 
> used in other marketing materials; they're used to give the reader a starting 
> point with your project. Keep the project description concise. One or two 
> paragraphs (no bullets) is preferred for the sake of consistency. The Project 
> Metadata page [4] provides some help to specify a project description (note 
> that I know the current mechanism is terrible, and am working on a much nicer 
> solution).
> 
> Thanks,
> 
> Wayne
> 
> [1] http://eclipse.org/projects/releases/releases.php?release=juno
> [2] 
> http://wiki.eclipse.org/SimRel/Simultaneous_Release_FAQ#How_do_we_join_the_simultaneous_release_train
> [3] http://eclipse.org/projects/releases/descriptions.php?release=juno
> [4] http://wiki.eclipse.org/Development_Resources/HOWTO/Project_Meta-Data
> -- 
> Wayne Beaton
> The Eclipse Foundation
> Twitter: @waynebeaton
> <138x38.png>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


[cross-project-issues-dev] Metadata for participating projects

2012-01-25 Thread Wayne Beaton


  
  
Greetings.

Projects participating in the Juno simultaneous release are listed
on the "Releases" page [1]. There are currently 67 projects listed
here. All projects that are participating in Juno must have already
flipped the participation bit as described in the wiki [2]. If your
project is missing from this list, then you probably haven't flipped
the bit; please contact the planning council through your PMC
immediately.

Please take a look at the releases page to make sure that the offset
is correct and that the project releases associated with your
project have been specified. Project releases specified in the
project metadata that occur on the day of the release are displayed
here. Note that the name provided for the release is normalized to a
three part version number; release names that do not contain
numbers, or are labelled as a milestone (e.g. "1.0.0M2") are ignored
(i.e. it's not enough to label your release "Juno", but you could
label it "8.6 Juno").

Please also take a minute to ensure that the description for your
project is suitable. These are displayed on the Project Descriptions
page [3] and may be used in other marketing materials; they're used
to give the reader a starting point with your project. Keep the
project description concise. One or two paragraphs (no bullets) is
preferred for the sake of consistency. The Project Metadata page [4]
provides some help to specify a project description (note that I
know the current mechanism is terrible, and am working on a much
nicer solution).

Thanks,

Wayne

[1] http://eclipse.org/projects/releases/releases.php?release=juno
[2] http://wiki.eclipse.org/SimRel/Simultaneous_Release_FAQ#How_do_we_join_the_simultaneous_release_train
[3] http://eclipse.org/projects/releases/descriptions.php?release=juno
[4] http://wiki.eclipse.org/Development_Resources/HOWTO/Project_Meta-Data
-- 
  Wayne Beaton
  The Eclipse Foundation
  Twitter: @waynebeaton
  
  

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev